Last value aggregations use volatile instead of atomics#8560
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8560 +/- ##
============================================
- Coverage 90.97% 90.93% -0.04%
+ Complexity 10206 10204 -2
============================================
Files 1013 1013
Lines 27166 27158 -8
Branches 3182 3180 -2
============================================
- Hits 24713 24696 -17
- Misses 1729 1738 +9
Partials 724 724 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
zeitlinger
approved these changes
Jul 2, 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.
Huge win in last value aggregation performance by ussing a volatile instead of atomics. The realization is that atomics aren't required because the tracking of whether values are recorded is done in the parent
AggregatorHandle, meaning the actual aggregator itself is never collected if there are no values. Thus it doesn't need to reset to an "unset" state.Hopefully this also reduces the variance of gauge performance cases, which have been unreliable.