stats/opentelemetry: Optimize slice allocations #7525
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.
First commit moves attribute construction under
if
to only construct them when they are used.Second commit uses
WithAttributeSet()
instead ofWithAttributes()
.This avoids copying the slice, which is not necessary for this code. Seehttps://github.com/open-telemetry/opentelemetry-go/blob/metric/v1.28.0/metric/instrument.go#L349-L368.Also, a bit of allocations can be removed by constructing the vararg slice one time vs when calling
Record()
each time.The above benchmark gives me these results:
Seehttps://go.dev/ref/spec#Passing_arguments_to_..._parameters.
RELEASE NOTES: None