cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

Neo4j Version 5 Slower with Data Import

carib
Graph Buddy

Hello,

I'm writing this post to see if people out there have similar thoughts or comments.

It seems like the processing time has increased in importing data in Neo4j version 5.3.x. With Neo4j version 4.4.x, it only a couple of minutes in creating graph databases while taking into account all the necessary precautions with node constraints and efficient MATCH/MERGE queries.

I rewrote the deprecated queries in version 4.4.x to import data so that they use the updated syntax and everything seems to be running slower in version 5.3.x. This change in particular with uploading data seems to running a lot slower (dataset that took minutes to upload now takes 30 minutes):

carib_0-1674061907608.png

Here's a list of the changes in syntax:

https://neo4j.com/docs/cypher-manual/current/deprecations-additions-removals-compatibility/

Anyone else out there with a similar experience?

Thanks

1 ACCEPTED SOLUTION

carib
Graph Buddy

Note to self. This solved my probelm.

https://neo4j.com/developer/kb/post-union-processing/#_post_union_processing_enhancements_in_4_1

This piece from the article improved the import query:

"You can get around all of these restrictions by simply introducing an additional WITH clause after the importing WITH, like so:"

The change from :auto PERIODIC COMMIT etc to the Call {} query format is making me implement a bunch of changes to the legagcy cypher from version 4.

Just out of curiosity, why were there such a large number of syntax changes from version 4 to version 5? I've been having to rewrite a lot of cypher.

I don't recall such large number of changes like these when working on SQL databases.

View solution in original post

1 REPLY 1

carib
Graph Buddy

Note to self. This solved my probelm.

https://neo4j.com/developer/kb/post-union-processing/#_post_union_processing_enhancements_in_4_1

This piece from the article improved the import query:

"You can get around all of these restrictions by simply introducing an additional WITH clause after the importing WITH, like so:"

The change from :auto PERIODIC COMMIT etc to the Call {} query format is making me implement a bunch of changes to the legagcy cypher from version 4.

Just out of curiosity, why were there such a large number of syntax changes from version 4 to version 5? I've been having to rewrite a lot of cypher.

I don't recall such large number of changes like these when working on SQL databases.