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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(metrics): Track memory footprint more accurately [INGEST-1132] #1288
fix(metrics): Track memory footprint more accurately [INGEST-1132] #1288
Changes from 6 commits
585ded8
aec39ce
734d952
b0c5a95
100f81f
66c19d5
975f1b9
0a70239
5764c12
8f82611
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did not run any benchmarks, but figured that a
HashMap
is a safer choice w.r.t. scaling.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's fine either way. btreemap might have an edge for small values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While at it, it would be good to deal with the
Occupied
branch too. See #1287 (comment)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
Occupied
branch is handled correctly (though not elegantly):relay/relay-metrics/src/aggregation.rs
Lines 1303 to 1306 in 5764c12
The advantage of computing the cost twice and subtracting is that we only need a single function for computing bucket value cost. If we did something like
added_cost = if something_added { value.incremental_cost() } else { 0 }
, we would need to also implement anincremental_cost
function onBucketValue
andMetricValue
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we call subtract_cost twice instead? then overflow/underflow handling is also dealt with in one place