Skip to content

fix(repair): bump max shred / sign in and increase default shred sets #7545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
lidatong merged 1 commit into from
Dec 3, 2025
Merged

fix(repair): bump max shred / sign in and increase default shred sets #7545

lidatong merged 1 commit into from
Dec 3, 2025

Conversation

@lidatong
Copy link
Member

@lidatong lidatong commented Dec 3, 2025

No description provided.

@lidatong lidatong requested a review from emwang-jump as a code owner December 3, 2025 21:59
@lidatong lidatong enabled auto-merge (squash) December 3, 2025 22:02
@github-actions
Copy link

github-actions bot commented Dec 3, 2025

Performance Measurements ⏳

Suite Baseline New Change
backtest mainnet-368528500-perf per slot 0.050864 s 0.0508 s -0.126% ✅
backtest mainnet-368528500-perf snapshot load 1.647 s 1.644 s -0.182% ✅
backtest mainnet-368528500-perf total elapsed 50.86362 s 50.799898 s -0.125% ✅
firedancer mem usage with mainnet.toml 1014.23 GiB 1023.23 GiB 0.887% ✅

@lidatong lidatong merged commit 32ed6f9 into main Dec 3, 2025
13 checks passed
@lidatong lidatong deleted the chali/fix/repair branch December 3, 2025 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@emwang-jump emwang-jump emwang-jump approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@lidatong @emwang-jump