storage/remote: speed up StoreSeries by re-using labels.Builder #13491
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.
Relabeling can take a pre-populated
Builder
instead of making a newone every time. This is much more efficient.
Added a benchmark to demonstrate:
Also simplify
processExternalLabels
taking advantage ofBuilder.Get
added recently.Switching
processExternalLabels
fromScratchBuilder
toBuilder
makes the code slower for the no-build-tags implementation oflabels.Labels
, which I can fix, but I figured I would wait to see if anyone is affected by this. Prometheus and Grafana Agent are both using-tags stringlabels
.