perf(l1): filter bloom counting using fastbloom instead of qfilter #5209
Conversation
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
Keeping a per layer bloom helps avoiding rehashing every time a bloom rebuild happens. This is because the bloom merge method uses the u64 hash keys directly instead of rehashing the value of type T. This is an improved version of #5175 where in addition to that we keep a per layer bloom to avoid extra hash work.
Lines of code reportTotal lines added: Detailed view |
Benchmark Block Execution Results Comparison Against Main
|
edg-l
force-pushed
the
filter_bloom_counting_fastbloom
branch
from
e574e4e to
d91f940
Compare
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.
Motivation
I think qfilter has a strong degradation when inserting and removing frequently, now I'm testing a pure counting bloom filter