Skip to content
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

chore(blooms): bloom_client records cache locality score #12458

Merged
merged 4 commits into from
Apr 4, 2024

Conversation

owen-d
Copy link
Member

@owen-d owen-d commented Apr 3, 2024

This is a helpful way to measure how effectively we distribute filter queries to bloom-gws. Should mostly converge to 1 once we start using jump-hash instead of the ring for these, but it'll give us a good way to measure that improvement.

Signed-off-by: Owen Diehl <ow.diehl@gmail.com>
@owen-d owen-d requested a review from a team as a code owner April 3, 2024 22:06
@owen-d owen-d changed the title bloom client records cache locality score chore(blooms): bloom_client records cache locality score Apr 3, 2024
Signed-off-by: Owen Diehl <ow.diehl@gmail.com>
Signed-off-by: Owen Diehl <ow.diehl@gmail.com>
Signed-off-by: Owen Diehl <ow.diehl@gmail.com>
@chaudum chaudum merged commit a6f3b93 into grafana:main Apr 4, 2024
10 checks passed
rhnasc pushed a commit to inloco/loki that referenced this pull request Apr 12, 2024
This is a helpful way to measure how effectively we distribute filter queries to bloom-gws. Should mostly converge to 1 once we start using jump-hash instead of the ring for these, but it'll give us a good way to measure that improvement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants