On Thu, Aug 28, 2014 at 3:25 PM, Chris Decker <[email protected]> wrote:
> Mike, > > :) > > I upgraded to 1.3.2 yesterday mid-afternoon. So far things feel much > snappier, but I wiped my ‘data’ directory so ES has less to search (though > most of my queries only go back 1 day anyways; I go back 3 days on Monday’s > to account for the weekend days I missed though). > Oh that's good to hear! > I wish I could get SSDs. The good news is that when I get these 4 > additional servers, ES will have a total of 248 GB of RAM, which should > allow quite a bit of data to be cached. > Good. > Do you have any guidelines for using warmers? From my understanding, they > help “warm up” the segments, so I have them defined in my template so that > the common term queries are executed automatically. I expected this to > make it so that when I hit a page that used those exact term queries, the > data would pretty much load instantly because it was in the cache. It > doesn’t appear they load instantly, though the warmers have seemed to help. > Well, you configure exactly what "warming" means (e.g., tell it which queries to run). But this doesn't mean the query results are cached: this process just warms up the OS's IO buffer caches. When you then run the same query later, it still must re-run all the query processing, it's just that the pages should be "hot" from the OS and we don't have to wait for disks to seek to those pages ... Mike McCandless http://blog.mikemccandless.com -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAD7smRdR7K-L7Uadx5QB7qX7TOJCegnkFmDOViiXJmuxKwNJnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
