Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.
06-15-2020 07:34 AM
We are currently using Java async driver with Neo4j 4.0.
I had a look at your presentation here where performance results, notably for memory consumptions, are presented to be very better with new Reactive driver.
I would like to know how far is the performance gap between the async and reactive drivers for READ queries with a significant amount of data.
For what I have understood from the documentation, async driver is just supporting flow control whereas reactive driver is working with a Publisher-Subscriber API under the hood. Tell me if I am wrong, but I understand that async driver is just doing some pull with static fetchSize value for batching records, whereas reactive driver is using dynamic push-pull. Am I right ?
So, can we expect a significant difference of performance between async and reactive drivers, in favor of reactive one when the amount of data is big ?
Thanks.
06-18-2020 12:57 AM
Hello,
I am also considering to use the Reactive Driver and I am having similar questions about the performance, could anybody answer the question, please.
Thank you
All the sessions of the conference are now available online