It's not uncommon for a Neo4j developer to have a query taking longer than desired.  Usually, the solution is to review and potentially tune the query.  However, for those newer to Neo4j, it makes sense to provide the following output to someone with more graph expertise to assist in reviewing the schema, data model and query performance.

 

For these commands, you will need access to Neo4j browser:

First: you can review your schema yourself or with a graph expert with the command:

:schema

Example:

Second: you can review your model yourself or with a graph expert with the command:

CALL db.schema.visualization

Example:

Third: you can analyze the performance of your query yourself or with a graph expert using PROFILE (run the query with 1,000 nodes).

PROFILE <query> LIMIT 1000

Example:

 

For a more comprehensive article on query performance tuning with Neo4j, please review: https://support.neo4j.com/s/article/4404022359443-Performance-tuning-with-Neo4j-AuraDB

For additional context on using EXPLAIN and PROFILE with query tuning, please review: https://support.neo4j.com/s/article/6638160188691-How-to-get-Cypher-query-execution-plans-using-EXPLAIN-and-PROFILE