storegateway: avoid unnecessary allocation in seriesForRefCacheKey
#3179
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.
Signed-off-by: Miguel Ángel Ortuño ortuman@gmail.com
What this PR does
According to a
storegateway
memory profile from the ops cluster, thestrconv.FormatUint
function used inseriesForRefCacheKey
is taking roughly1.37%
of total allocated objects. That seems quite a lot for just an id generator function.This PR adapts
seriesForRefCacheKey
to parse series ref id using a stack a buffer to avoid unnecessary allocations.Below are the benchmark results comparing against the old implementation:
Previous:
Current:
Comparison:
Which issue(s) this PR fixes or relates to
Fixes N/A
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]