opentelemetry-sdk: make 'consume_measurement' lock free#5321
Merged
lzchen merged 3 commits intoJun 18, 2026
Merged
Conversation
Contributor
|
@herin049 Thanks for the quick fix, I had a look and the change seems good. Sorry about any issues caused by the last PR. |
xrmx
approved these changes
Jun 18, 2026
MikeGoldsmith
approved these changes
Jun 18, 2026
DylanRussell
approved these changes
Jun 18, 2026
lzchen
approved these changes
Jun 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR fixes a deadlock scenario with
consume_measurement()inSynchronousMeasurementConsumerby changing_reader_storagesto use COW semantics.The original PR #4863 also introduced a significant performance regression as seen in the benchmarks here: https://opentelemetry.io/docs/languages/python/benchmarks/
This fix brings the performance close to the performance before these changes were introduced:
Fixes #5313
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Does This PR Require a Contrib Repo Change?
Checklist: