FlatMap overloads with maximum concurrency parameter#2627
Merged
benjchristensen merged 1 commit intoReactiveX:1.xfrom Feb 11, 2015
Merged
FlatMap overloads with maximum concurrency parameter#2627benjchristensen merged 1 commit intoReactiveX:1.xfrom
benjchristensen merged 1 commit intoReactiveX:1.xfrom
Conversation
Member
|
👍 |
benjchristensen
added a commit
that referenced
this pull request
Feb 11, 2015
FlatMap overloads with maximum concurrency parameter
Member
Author
I was wrong with this statement. Depending on the request pattern, reordering may still happen and the downstream may be still slower. Unboundedness of Having the |
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.
For issue #2626.
There is no point in adding maxConcurrent to flatMapIterable because each iterable is subscribed to sequentially and run to completion.