perf(bigtable): Refactor metric attributes for performance #12445
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.
Documentation of WithAttributes is :
In this PR, the
toOtelMetricAttrsfunction inbigtable/metrics.gohas been modified to return anattribute.Setinstead of a[]attribute.KeyValueslice. This allows for more efficient attribute handling.So, earlier
Now,
This should lead to performance gain since the copy step is eliminated
Below are the pprof flame graphs of 10 Go routines reading a million rows. Top is without the changes in this PR and bottom is with changes in this PR.


In this run, recordOperationCompletion took 16.36% lesser time.
Repeated the same again


In this run, recordOperationCompletion took 17.97% lesser time.