I’ve been running into an issue where the neo4j browser and bloom start lagging or even freezing when I run long or complex cypher scripts on larger datasets. I was chatting with a friend about how some people use scripts with executors to automate and test workloads in other environments, which made me wonder if something similar could help here for stress-testing or isolating performance problems.
Has anyone else seen neo4j slow down like this with heavy queries? Are there best practices for breaking up scripts, using batching, or running them in a way that doesn’t lock up the UI?
@karinajohnson2812 - I am sorry I just noticed this as it was in a general category. Which version of our Neo4j platform are you working with (Aura, Community Edition, etc..)?
Also, although you can use the browser, and as you state
>>to automate and test workloads in other environments
Browser not only runs the cypher but then renders the results and if results are large and graphical this may had additional overheard.
If i was to simply want to test performance of scripts in a very light weight way I might use cypher-shell Cypher Shell - Operations Manual
one could run as
./cypher-shell -f /home/script.cyp
where /home/script.cyp includes you cypher statements