-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-27241 Add metrics for evaluating cost and effectiveness of bloom filters #4669
Conversation
…m filters - Add static index/bloom sizes - Add metrics for bloom requests and negative results
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing terribly surprising here, and I learned a bit about how metric aggregation at the table level works. Thanks!
Thanks Nick! |
…m filters (#4669) Signed-off-by: Nick Dimiduk <ndimiduk@apache.org>
…m filters (#4669) Signed-off-by: Nick Dimiduk <ndimiduk@apache.org>
Combined these together are very useful for determining whether you should add bloom filters (if eligible requests is high) and whether they are worth the cost (compare bloom size to bloom request/negative result count)
I added a test in TestHStore because I mostly wanted to verify that these new request/negative/eligible counts make it through the entire stack end-to-end, since it involves plumbing into a few classes.