"CYPHER 2.1.EXPERIMENTAL" tells Cypher to use a new query planner that we are working on. The runtime is the same and the parsing is the same, but the planning is different.
The new planner will sometimes make better plans than the old one, and sometimes make worse plans. Which it is depend on both the query, the structure of your data, and the particular version of the planner you happen to have. So basically the only way to know, is to just try it out and see how it behaves for your particular queries on your particular data. We intend to make the new planner the default when it is sufficiently consistent in making plans that are at least as good as the old planner. -- Chris Vest System Engineer, Neo Technology [ skype: mr.chrisvest, twitter: chvest ] On 16 Oct 2014, at 12:08, Alex winter <[email protected]> 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. -- 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.
