AtomicLongPosition plain methods fix. #322
Merged
Conversation
This file contains 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
The methods get and set, which have plain semantics, where calling AtomicLong.get/set which have volatile semantics. So they were calling methods with were more thread-safe than needed.
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.
The methods AtomicLongPosition.get and AtomicLongPosition.set, which have plain semantics according to the documentation, are calling AtomicLong.get/set which have volatile semantics. So they are calling methods that are more thread-safe than needed, leading to a potential performance penalty.
The same methods on the UnsafeBufferPosition, do call the right plain methods.