Re: Performance as a sql result cache

2014-06-11 Thread Dean Pehrsson-Chapman
ISWYM - down to 6ms now. Thanks again. On Wednesday, 11 June 2014 17:30:11 UTC+1, Dean Pehrsson-Chapman wrote: > > I was - but only about 20 times. I'll go back and have another look. >> Thanks. >> > -- You received this message because you are subscribed to the Google Groups "elasticsearch

Re: Performance as a sql result cache

2014-06-11 Thread Dean Pehrsson-Chapman
> > I was - but only about 20 times. I'll go back and have another look. > Thanks. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr.

Re: Performance as a sql result cache

2014-06-11 Thread joergpra...@gmail.com
You should run your search query more than just once. The first time executed, ES will load the Lucene index fields, and ramp up internal resources, which adds some overhead. Subsequent queries will be faster (around 1ms on my MacBook Pro with SSD but SSD is not important, it is the filesystem cach

Performance as a sql result cache

2014-06-11 Thread Dean Pehrsson-Chapman
Hi, I'm assessing ES as a tool to help with a specific problem. We have some expensive sql to run against a database that takes 300ms. there are 1000 or so rows, so we need to page over these results. I though ES would be a perfect tool to do this, but the results I've seen, while being rea