CompositeSubscription with atomic field updater#1236
Merged
benjchristensen merged 1 commit intoReactiveX:masterfrom May 21, 2014
Merged
CompositeSubscription with atomic field updater#1236benjchristensen merged 1 commit intoReactiveX:masterfrom
benjchristensen merged 1 commit intoReactiveX:masterfrom
Conversation
|
RxJava-pull-requests #1137 SUCCESS |
Member
There was a problem hiding this comment.
For my education can you explain what you mean by this comment?
Member
Author
There was a problem hiding this comment.
On x86 and with Java 8, getAndSet is compiled to LOCK XCHG instead of looping and trying to CAS in the new value. This may be true for other platforms. Since now the swap-in of the terminal state is fully atomic, concurrently running add or remove loops will stop faster. Previously, since everybody looped, it was more likely an add succeded before unsubscribe did. This might not be of concern just I wanted to explain the reason behind the use of getAndSet here.
benjchristensen
added a commit
that referenced
this pull request
May 21, 2014
CompositeSubscription with atomic field updater
Closed
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
3 participants
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.
This PR is aimed at #1204 to reduce unnecessary memory overhead in frequently used classes. This change in
CompositeSubscriptionsaves about 24 bytes per instance.In addition, the field updaters may be faster by about 8-15% for small adds and removals. I've changed the implementation of unsubscribe to use getAndSet which leverages platform intrinsics and is usually compiled to a single instruction: this makes unsubscribing a tiny bit faster and thus reducing latency in benchmarks that only pass on single element around.