feat: micro-optimize eth_getLogs#8
Closed
thaodt wants to merge 8 commits into
Closed
Conversation
…adigmxyz#16668) Signed-off-by: 7suyash7 <suyashnyn1@gmail.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
thaodt
force-pushed
the
feat/eth_getlogs_optz
branch
from
e071d6c to
02d3934
Compare
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
7 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.
the current
eth_getLogsbehavior supports two types of block filtering:AtBlockHash: Gets logs for a specific block by hashRange: Gets logs for a range of blocksFor range queries, it processes blocks in chunks of max_headers_range (1000 blocks) and uses bloom filters to quickly skip blocks that can't contain matching logs, then fetches receipts and logs only for blocks that might contain matches.
I've updated to process chunks of blocks in parallel for
get_logs_in_block_range_inner()fn, I'm profiling it but at a first sight, here is what I had so far.Basically for small ranges (1 chunk or less), I still apply the current approach.