My first guess with that big a difference would be a bug in the
calculation/output of the benchmark timing!
-Original Message-
From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On
Behalf Of Martin Grimmer
Sent: Tuesday, November 16, 2010 4:47 AM
To:
It's possible that you're seeing a GC spike. Would you mind adding GC
monitoring[1] to your output to see if that is related?
Best,
Andreas
[1]
http://www.oracle.com/technetwork/java/gc-tuning-5-138395.html#0.0.0.Measurement%7Coutline
On Nov 16, 2010, at 8:09 PM, Rick Bullotta wrote:
My
Do you have some nodes in your dataset which has loads of relationships?
Because if that's the case then the slow query could possible hit one or
more of those heavy nodes.
Also are you using breadth first traversal from one direction or from both
directions (both directions being much more
3 matches
Mail list logo
