-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poor Save Performance Compared to Neo4j OGM #2636
Comments
Hi, thank you so much for raising this issue. I was expecting some difference in perfomance using SDN and OGM but I wouldn't say it is that big. I will give it at try after holidays. |
I have seen this and of course we want to improve your situation. Sorry for not interacting with the issue until now. |
Update: I am still on this topic but have to rethink a few bits in there. There were some test failures and after correcting those the alternative version is more or less equal up to 10000 relationships 😞 |
Any update? |
Unfortunately as mentioned beginning of this year, the prefetching did not succeed. |
When using non-simplistic graphs (graphs with multiple relationships between nodes or more connected graphs), the Neo4j OGM vastly outperforms SDN in saving data to a graph (tested using sdn 6.3.3 and sdn 7.0.0 and comparing against Neo4j OGM 3.2.38, also tested both Neo4j DB 4.4 and 5.2). In graphs consisting of only nodes, or nodes with 1 relationship the performance is comparable.
Here are links to the 2 example projects comparing the projects. On my laptop (M1 Pro CPU) the SDN is ~4 times slower than the OGM. In my work with a more complex schema it's ~10 times slower. The SDN example project has 2 branches, with master using SDN 6.3.3 and the other using SDN 7.0.0. In either project there's a test you can run and logging to show how long it takes to load an object after a warmup period.
SDN Example
OGM Example
The text was updated successfully, but these errors were encountered: