1.x: benchmark just and Single #3982
Merged
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 adds a comparison benchmark for working with
Observable.just
andSingle.just
.Results: (i7 4790, Win 7 x64, Java 8u92)
one
: custom Observable emitting a single item with backpressurescalar
:Observable.just(1)
scalarHidden
:just(1).asObservable()
single
:Single.just(1)
singleHidden
: wrapping withSingle.create
plain
: just subscribeConcat
: useconcatMap
to map it to a scalar (operator not available in Single)Merge
: useflatMap
to map it to a scalar/singeSwitch
: useswitchMap
to map it to a scalar (operator not available in Single)My guess is that single is slower because that
Observable.OnSubscribe
vsSingle.OnSubscribe
wrapping game.