Hi @ameyasoft ,
I’ve already checked the indexing and constraints, and everything appears to be in place. I didn’t need to create them manually—they were automatically created when I imported the old dump into the Neo4j v5 database. All indexes follow the new format (e.g., range and text), so I don’t believe there’s any issue on that front.
Additionally, I compared the same query on both the old and new databases and found that the new database actually executes the query faster. However, the final response in the application seems slower.
I'm starting to suspect that this may be due to the older version of GraphQL being used in the project, which I haven’t updated during the migration from Neo4j v4 to v5.
Is it possible that the new Neo4j driver isn't fully compatible with the older GraphQL version, and that’s what’s affecting performance?
For more context on the package versions, please refer to my previous messages in this thread.