What is the maximum amount of data supported by a query
Could you be more specific? Do you mean something like how much data can you return from Neo4j to the client in a single query? Or something like how many nodes can a given query traverse? Or how much data can be loaded into Neo4j in a single query?
Thank you very much for your reply. I deployed the community version of neo4j as a singleton, and then used neodash to write a query to query the data. The phenomenon is as follows: if the query data is large, timeout will be returned. I would like to ask you what is the maximum amount of data supported by match in neo4j community Edition at one time? How to avoid such problems? Is there a similar problem if multiple people access the site at the same time？
I would try running the query that you are using in Neodash directly in Neo4j using Neo4j Browser or Cypher shell to see if there is a specific error returned by Neo4j. Or are you seeing an error message reported by Neodash?
what is the maximum amount of data supported by match in neo4j community Edition at one time?
This is basically getting at how much transaction state can be built up in a single query, whis is determined by the server.memory.heap.max_size (how much memory on the machine is made available for Neo4j transactions, essentially) and the db.memory.transaction.max setting (per transaction).
See this page for more info:
If your query is just returning too much data to the client there can also be timeouts associated with sending too much data to a web application.
Thank you very much for your answer. I have probably understood some reasons. The previous mistakes are as follows "The transaction has been terminated. Retry your operation in a new transaction, and you should see a successful result. The transaction has not completed within the specified timeout (db.transaction.timeout). You may want to retry with a longer timeout. ". Will making the db.transaction.timeout parameter larger solve the problem?
