1.x: optimize concatMapIterable/flatMapIterable #3864
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 reduces the overhead of
concatMapIterable
/flatMapIterable
by not wrapping them intoObservable.from
sources but handling the generatedIterable
s directly.Since
Iterable
s are inherently synchronous, there is no difference between the two operators that now use the common underlying operator (i.e., flatMap can't chose a different source because it can't tell if anIterable
source is not ready or not;hasNext()
is for indicating completion, not temporary lack of data).Benchmark (i7 4790, Window 7 x64, Java 8u77):
Iterable-M
is the current master,Plain
is usingconcatMap(Observable::from)
as a reference.The
count=1
cases are bit slower because there is no good way of detecting if anIterable
holds only a single element, unlike withjust()
, and have to instantiate the full infrastructure even for a single element.The same table using the master as baseline: