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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding two level hashing in metrics hashmap #1564
Adding two level hashing in metrics hashmap #1564
Changes from 23 commits
98db4f3
1c440e0
75c853e
fd858f6
1f05dcf
d191cf7
fd94caa
da817b5
498f088
2930fe1
ebe4a38
d8cbc4c
cad1391
61ae262
2b8549f
44efee7
d8c56da
7b0bac5
61c8b0d
267e305
078c994
cc12da1
90bbb2d
f89c3ea
603305e
21b0b3e
f33729c
8b48564
04c68c2
fdb5020
d973c4d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in the common path where attributes are already existing, now we have to acquire lock once, do lookup, release lock, and the re-acquire the lock, and do the lookup+update.
Apart from the perf hit, this loses the atomicity of the update. It is possible that, between the time we release the lock and re-acquire, other entries might have occurred and the limit was hit, so this attribute should be going into over-flow.
We need to ensure atomicity and avoid the two-step lock-release-re-lock.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good observation, made the required changes. All operations should be (theoretically) atomic now, and perf should be fast for common scenarios of attributes already existing.
Check warning on line 216 in opentelemetry-sdk/src/metrics/internal/sum.rs
opentelemetry-sdk/src/metrics/internal/sum.rs#L211-L216
Check warning on line 302 in opentelemetry-sdk/src/metrics/internal/sum.rs
opentelemetry-sdk/src/metrics/internal/sum.rs#L298-L302
Check warning on line 359 in opentelemetry-sdk/src/metrics/internal/sum.rs
opentelemetry-sdk/src/metrics/internal/sum.rs#L358-L359
Check warning on line 412 in opentelemetry-sdk/src/metrics/internal/sum.rs
opentelemetry-sdk/src/metrics/internal/sum.rs#L405-L412
Check warning on line 490 in opentelemetry-sdk/src/metrics/internal/sum.rs
opentelemetry-sdk/src/metrics/internal/sum.rs#L484-L490
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will create an issue for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will create an issue for this.