That percent thing is Mark running the query a number of times to get a more accurate impression about the run speed.
It's on Git here <https://github.com/mneedham/cypher-query-tuning> or specifically query_profiler.py <https://github.com/mneedham/cypher-query-tuning/blob/master/query_profiler.py> . Min will then by the fastest run, Max the slowest and then a couple of percentile values in between. So run 2.1 Experimental, run all your favorite queries but it's not going to tell you itself what a great job it did! M On Thursday, 16 October 2014 11:08:33 UTC+1, Alex winter wrote: > > Hi. > I read that we could use CYPHER 2.1.EXPERIMENTAL prefix to improve the > performance of query. > But what kind of queries we can apply this? > Because if i use this for simple query, it doesn't show some thing like % > as in the article: > > http://java.dzone.com/articles/neo4j-set-based-operations > And what the meaning of min, max:? > Min 0.719580888748 50% 0.723278999329 95% 0.741609430313 Max > 0.74364614486707. > > > Thanks in advance. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
