Hey all, I was testing the speed of neo4j-driver (1.6.2 and 1.7.1) and py2neo (4.1.3) and I found that the simple HTTP requests that I was doing are 2-5 times faster for medium sized queries and up. I'll take you through what I did, so we can hopefully figure out what's going on here and when it ma…

Thanks a lot for the feedback. I think mostly the difference is between the network & stream processing code. For requests this will go down to c-code while the bolt-drivers are doing it in python. It would be good if you could re-run it in 3.5.x to see if the server makes a difference. Also as f…

Hey hey, I copied the data that I was testing with to the current docker version of neo4j:3.5 and the results are very similar. This is only tested with neo4j-driver 1.6.2, because this is the version that py2neo 4.1.3 requires, so I can test both drivers with the same virtual env. For completenes…

Also, I just noticed that if you're married to py2neo, then it's better to use it with the http scheme if you're firing multiple queries in a single transaction, whereas the bolt scheme is more preferable for retrieving many nodes in 1 query.

I have now also tested the neo4jrestclient library (v 2.1.1), and it's pretty similar to the HTTP requests, except for larger queries where it's almost exactly a factor 2 slower. I've also tested what happens when I add the 'X-Stream: true' header in the HTTP request (as suggested in the developer …

X-Stream: true was only needed for the old (now removed REST API). The transactional endpoint streams automatically (in and out) (but you should stream-process the results to benefit from that). neo4jrestclient is no longer maintained though. And you can use the tx endpoint with multiple transact…

Hi @jjbankert Thank you massively for the time and effort you've put into this. There's a lot of interesting data to sift through there and it's extremely valuable for us, and no doubt for other people too. Firstly, it's worth pointing out that the original Bolt project was never about trying to o…

I'll check-out seabolt! I agree that there are a multitude of reasons to choose one driver over another. My use-case is to perform big updates on many nodes at once. Batch queries that return 10k-100k nodes and batch updates of 10k-100k statements are pretty standard for me. I was hoping that there…

Is there somewhere I can see your test code?

Summary I performed some similar testing for API Endpoints using a Py2neo Bolt + Lambda/Chalice app in AWS vs using the Barebones HTTP request and found the following results. The request being tested is to pull entire subgraphs of upto 4 hops away from a specific Node Id in the database. The Ids ar…

Interesting stuff @benjamin.squire ! I'm in the final stages of open-sourcing my driver (got the go-ahead from management), so expect that soon. First time making 'production' python code, so lots to figure out, and of course there's the problem of coming up with a good name. @technige somehow I mi…

Barebones HTTP requests much faster than python neo4j-driver and py2neo?

Drivers & Stacks Python

jjbankert (Jjbankert) January 22, 2019, 5:43pm 12

As promised, our project is now open-source and available: Announcing neo4j-connector 1.0.0 (python 3.5+)

Topic		Replies	Views
Should I use HTTP API or Driver API? Drivers & Stacks	6	2059	May 20, 2021
Slow streaming with neo4j driver compared to py2neo Drivers & Stacks py2neo , neo4j-driver , streaming	0	574	July 26, 2021
Announcing neo4j-connector 1.0.0 (python 3.5+) Python	4	2643	March 7, 2019
Performance problem Python performance , cypher	18	3555	September 30, 2018
Neo4j JS Driver slow response Drivers & Stacks neo4j-driver , js-driver	2	946	June 5, 2020

Barebones HTTP requests much faster than python neo4j-driver and py2neo?

Related topics