Mimir query engine: report estimated peak memory consumption as a metric and in traces #8270
Conversation
This file contains 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
jhesketh
approved these changes
Jun 6, 2024
charleskorn
force-pushed
the
charleskorn/report-estimated-memory-utilisation
branch
from
c731381
to
db15467
Compare
4 tasks
narqo
pushed a commit
to narqo/grafana-mimir
that referenced
this pull request
Jun 6, 2024
…ric and in traces (grafana#8270) * Add histogram with estimated peak memory consumption of each query * Include estimated peak memory consumption in traces. * Add changelog entry
2 tasks
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.
What this PR does
This PR builds upon #8230 to add reporting of the per-query estimated peak memory consumption.
The estimate is reported as a metric and in a
query statsevent added to the query's trace span.Note that for consistency with the metrics added in #7898, I've used the prefix
cortex_streaming_promql_engine...for the metric name. I'll change the name to reflect the new name for the engine in a separate PR.Which issue(s) this PR fixes or relates to
(none)
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX].about-versioning.mdupdated with experimental features.