Reuse aggregation handles for delta temporality #5176
Merged
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.
After recent changes, cumulative aggregations now use the same
AggregationHandle
over the course of their life, resulting in lower allocation than delta, which issue newAggregationHandle
instances after each collect. This isn't necessary - after collecting and reseting, theAggregationHandles
are back to their initial state and can be reused.The result is a >50% memory allocation reduction for delta instruments. Pretty slick for just a handful of lines of code!
Performance benchmarks before:
And after:
Notice how memory allocation for cumulative and delta temporality are now in line with one another.