promql: faster range-query of label_replace and label_join#13536
Merged
beorn7 merged 2 commits intoprometheus:mainfrom Feb 29, 2024
Merged
promql: faster range-query of label_replace and label_join#13536beorn7 merged 2 commits intoprometheus:mainfrom
beorn7 merged 2 commits intoprometheus:mainfrom
Conversation
These functions act on the labels only, so don't need to go step by step over the samples in a range query. Signed-off-by: Bryan Boreham <bjboreham@gmail.com>
Signed-off-by: Bryan Boreham <bjboreham@gmail.com>
3 tasks
Member
|
This seems to have broken the data + query case where series are not duplicate at individual steps of a range query, but become duplicates when combining the outputs of multiple independent range query steps, as reported in #15114 |
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.
These functions act on the labels only, so don't need to go step by step over the samples in a range query.
I'm not entirely happy about the
switchthat calls the new version, but it is in line with some previous changes.I think the whole of
evalandevalRangeshould be refactored to make it easier to understand.I left the previous entry-points in place with a
panic, to make it obvious if someone is calling them in a way I didnt know about.Benchmarks