Repository navigation
Add verification batch size configuration - #5
Merged
Merged
Conversation
Configurable batch sizes for chain verification to balance memory usage against store round trips during large audits.
PrimelPJ
commented
Oct 20, 2026
PrimelPJ
left a comment
PrimelPJ
left a comment
Owner
Author
There was a problem hiding this comment.
Good defaults. 1000 per batch with 50k progress interval should keep long verifications responsive without flooding logs.
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
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.
Adds constants for controlling batch size during chain verification. DefaultVerifyBatchSize (1000) balances memory against round trips. MaxVerifyBatchSize (10000) prevents OOM on stores with millions of events.