promql: benchmark for join queries with more labels#17130
Merged
bwplotka merged 3 commits intoprometheus:mainfrom Oct 24, 2025
Merged
promql: benchmark for join queries with more labels#17130bwplotka merged 3 commits intoprometheus:mainfrom
bwplotka merged 3 commits intoprometheus:mainfrom
Conversation
Signed-off-by: Linas Medziunas <linas.medziunas@gmail.com>
Contributor
Author
|
Sample output: |
Signed-off-by: Linas Medziunas <linas.medziunas@gmail.com>
beca574 to
2a9ba3a
Compare
bwplotka
reviewed
Oct 24, 2025
Member
bwplotka
left a comment
There was a problem hiding this comment.
Epic! Some small questions / readability nits only, but generally great 💪🏽
bboreham
reviewed
Oct 24, 2025
Signed-off-by: Linas Medziunas <linas.medziunas@gmail.com>
a032b05 to
dee96f7
Compare
Contributor
Author
bwplotka
approved these changes
Oct 24, 2025
Member
|
Thanks! |
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
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.
I am working on a series of changes that will improve PromQL binary vector matching (AKA "joins") significantly. For evaluating the impact, I could not find any useful benchmarks.
The ones in bench_test.go only have one label
lwith values from0to99:prometheus/promql/bench_test.go
Lines 61 to 62 in 11c4915
But PromQL join performance heavily depends on the length of label sets, and in practice we see label sets that are at least hundreds of bytes long. Therefore I am submitting this new benchmark which I intend to use for evaluating join performance.
Does this PR introduce a user-facing change?