3.x: Performance improvements (tracking issue)
See original GitHub issueI assembled a fresh evaluation of RxJava 1, 2 and Reactor 3.2 performance under various usages and found the following deficiencies in RxJava 2.
-
Flowable.empty()
appears to be consuming a lot of memory. - See if a non-trampolining
Schedulers.from
could improve async/pipeline performance. - Check why
Observable.blockingLast
has 30% more overhead than itsFlowable
counterpart. - Check why there is a lot more overhead with
ReplayProcessor
andReplaySubject
compared to v1. - Check why there is a lot more overhead with
UnicastProcessor
andUnicastSubject
compared to v1. - Check why
Observable.fromArray
is somewhat slower with longer sources thanFlowable
. - Check why
Observable.fromIterable
is slower with longer sources thanFlowable
. - Optimize
Observable.concatMap
for scalar inner sources. - Check why
Flowable.flatMapIterable
is drastically slower thanObservable
and Reactor’s version in just/range/crossmap scenarios.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:17
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Tracking Down Performance Tuning Issues | Datavail
An important first step to take well before any changes are made to the system is to carefully evaluate the various components, including ......
Read more >Performance Tuning SQL Server Change Tracking
Let's say I'm using Change Tracking to move data to a secondary SQL Server. Normally it polls data every hour, but there's a...
Read more >A guide to issue trackers (+3 best issue tracking software)
An issue tracker records all customer problems. Learn why it's the all-in-one solution for streamlining your customer support experience.
Read more >Viewing all of your issues and pull requests - GitHub Docs
The Issues and Pull Request dashboards list the open issues and pull ... For better performance, improved security, and new features, upgrade to...
Read more >Explore best practices for Spark performance optimization
Learn some performance optimization tips to keep in mind when developing your Spark applications.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You can try that. Ops/second is the usual measure for us.
Different JVM versions give different results and I don’t see any clear optimizations to make them better across. I’ll close it for now.