-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paired Block Bloom Filter Algorith - BPK Adjustment to avoid performance degradation with bpk<=10 #161
Comments
Pull request: #163 |
Performance needs to cover a few tests. |
Pass performance tests |
@erez says he has checked a branch named pared_bloom_filter-improved |
udi-speedb
added a commit
that referenced
this issue
Dec 14, 2022
udi-speedb
added a commit
that referenced
this issue
Dec 18, 2022
Yuval-Ariel
pushed a commit
that referenced
this issue
Dec 18, 2022
Repository owner
moved this from 🏗️ Working on it
to 📖 Need your Opinion!
in Speedb Roadmap
Dec 18, 2022
Yuval-Ariel
pushed a commit
that referenced
this issue
Apr 30, 2023
Yuval-Ariel
pushed a commit
that referenced
this issue
May 4, 2023
udi-speedb
added a commit
that referenced
this issue
Nov 13, 2023
udi-speedb
added a commit
that referenced
this issue
Nov 15, 2023
udi-speedb
added a commit
that referenced
this issue
Dec 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During @noamhaham's performance runs, he discovered that there is a performance degradation with the paired filter with bpk=10.
suggests to adjust the user's bpk (round up) to end up in an effective bpk that is larger that the user's. This adjustment implies more memory consumption for the filters (relative to not rounding up). The more keys a filter has, the smaller the adjustment / memory-consumption-increase and vice versa =>
Noam expects this to be felt more in Level 0 and less as the level progresses. However, since most of the data is in the lower levels, he expects the total consumption increase to be negligible.
The text was updated successfully, but these errors were encountered: