Optimize metrics tracking on ingester v2Push() errors #3969
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.
What this PR does:
I'm profiling the ingester
v2Push()
to investigate why we see increased CPU and memory on an high number of errors occurring in the write path (eg. out of order samples, out of bound samples, per-user/metric series limit reached). I've improved the benchmark we already had and I've found out several inefficiencies.This is the first PR to fix a single issue: metrics tracking. I will follow-up with dedicated PRs for other improvements.
Benchmark:
Which issue(s) this PR fixes:
N/A
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]