Repository navigation
1.x: measure flatMap/concatMap performance when used as filter - #3754
Merged
Merged
Conversation
akarnokd
added a commit
that referenced
this pull request
Mar 13, 2016
1.x: measure flatMap/concatMap performance when used as filter
Collaborator
|
Thanks @akarnokd, very good of you. I'll set up a PR to use it. |
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.
This PR adds a perf class to measure the overhead of using
empty()when theflatMap/concatMapemulatesfilter.This will establish the comparison baseline for
flatMap/concatMapoptimization as requested in #1653.The baseline numbers (i7 4770K, Windows 7 x64, Java 8u72):
Comparing
flatMapagainstconcatMap:Here, mask indicates the and-mask that makes emitting
emptyless frequent: 0 = always, 1 = every other, 3 = every fourth, 7 = every eighth. This also means thatrangeEmptystarts emitting more and more values with higher mask value hence the different throughput values.