Tom, I think it is an CPU issue, I only have this single change in my neo4j-shell file:
EXTRA_JVM_ARGUMENTS="-Xmx6G -Xms6G -Xmn1G -XX:+UseConcMarkSweepGC -server" as I don't run against server but if you run against server the performance should be the same. I think on your hosted server (Digital Ocean) the CPU performance affects the query time. Unfortunately my computer crashed and I lost my scratch-file with my queries for your case that I was experimenting with. Will take a while to redo that. I think it is related to some implementation details in Cypher's path handling, but have to investigate further. Michael Am 11.03.2014 um 09:29 schrieb Tom Zeppenfeldt <tomzeppenfe...@gmail.com>: > Hi Michael, > > could you perhaps share your neo4j-shell for me to learn from. I'm still very > far away from the 1.6 secs that you were able to achieve. > > Best, > > Tom > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to neo4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
