execution/stagedsync: bump ChangeSets3 chain-tip prune limit#21216
Merged
Conversation
…00000 On heavy-state chains (bloatnet) the 1000-entry per-call cap drains ~85x slower than ChangeSets3's creation rate once initialCycle=false. The 2s timeout still bounds wall-time; 200k just removes the artificial floor on how many entries one call can touch.
AskAlexSharov
approved these changes
May 16, 2026
AskAlexSharov
left a comment
Collaborator
There was a problem hiding this comment.
Maybe we don’t need limit - and need only time-budget.
Because delete 10k of keys when db > ram is slower than delete 10m keys when db fits in ram.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #21204 to main.