Avoid exemplar allocations if there are no measurements #5182
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.
This change is part of the #5178 but can be considered separately.
I noticed that a decent amount of allocations happen in exemplar classes even when exemplars are disabled. The culprit is that we when collecting, we allocate a
new ArrayList<>()
even when a reservoir has received no measurements.Performance before:
And after:
A nice improvement, probably on the order of ~10%.