If you used order by limit it had to pull through all data anyway even if you just returned a few rows, so your cache is filled and also the JIT got a chance on optimizing byte code. And it built a plan if you used parameters.
For warming up the cache, just run the queries you want to run fast. On Tue, Apr 22, 2014 at 6:51 PM, Alex Frieden <[email protected]> wrote: > One thing I have noticed is if I run a query and limit the results to a > small number then run it on the larger sets the time it takes goes from > minutes down to under eight seconds. What has anyone done to take > advantage of the warm cache. Obviously I would like to be able to get the > fast query speed of the warm cache. Do I just need to run several queries > in succession? > > -- > 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.
