[performance] enforce block-snapshots cap inside aggregator collation#20966
Merged
Conversation
- https://github.com/erigontech/erigon/pull/20701/changes was added, wherein the cap was passed to BuildFiles* api - but BuildFilesInBackground can ignore the passed txnum value (considering `lastTxNumInDb` etc.) - this PR moves the state collation cap logic inside the aggregator; the aggregator then needs a `SetFrozenBlocksProvider` which is called to find block snapshots progress, and use it to cap the state collation.
wmitsuda
approved these changes
May 7, 2026
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
3 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 #20852 to performance.
performance-specific adaptations
Resolved trivial conflict in
db/state/aggregator.go(addedSetFrozenBlocksProvidermethod).