feat: check snapshot range on ProviderFactory
#6608
Merged
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.
DatabaseProvider
.BlockchainProvider
should callProviderFactory
methods in instances where it can. Example:self.database.provider()?.header_td_by_number(number)
->self.database.header_td_by_number(number)
.Improvements apply to methods that might skip opening a Database transaction if all the necessary data is available to query the static file data.
Holesky with
maxperf
For equality tests, I run
b3sum
over the resulting csv and compareI feel like
cryo
still has some big overhead on writing/handling the incoming data, but this seems like a clear improvement. Also, oncryo blocks
the flamegraph hits onrpc_block
went from 19k (feat/static-files) to 500 (this branch)