It depends how likely it is for you to run the same aggregation again. Note
that this cache is fully invalidated at every refresh (meaning either every
second by default, or every time that you update/add/remove documents if
you perform less than 1 operation per second). So this cache will only be
used if you are likely to run the exact same request twice or more in a
short period of time.

We assumed that this situation is not common, so a small cache would be
enough for the maybe 4 or 5 requests that would be run again and again. You
can increase it if you think it will be helpful in your case although I
would advise to be careful, maybe memory would be better spent on eg. the
filesystem cache.

On Thu, May 21, 2015 at 3:41 PM, Mike Sukmanowsky <
mike.sukmanow...@gmail.com> wrote:

> Hi all,
>
> We store Marvel-style timeseries data in Elasticsearch and make very heavy
> use of aggregations (all queries are effectively aggregations).
>
> We've been playing around with the shard query cache and have a question.
>
> Is there a reason the shard query cache is set to such a low level of JVM
> heap by default? 1% seems awfully low unless ES assumes most people aren't
> making heavy use of aggregations? Any harm in us significantly boosting
> this from 1% to say 15% of heap? Most of our machines have 30GB of RAM and
> heap at 50% of that (15GB) so the query cache is 150MB by default. Think
> we'd like to experiment growing that to at least 10% of heap to have 1GB in
> use for this cache.
>
> Mike
>
> --
> Please update your bookmarks! We have moved to https://discuss.elastic.co/
> ---
> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/a3a0fa7b-49f8-4d78-a520-6eeb16d53de3%40googlegroups.com
> <https://groups.google.com/d/msgid/elasticsearch/a3a0fa7b-49f8-4d78-a520-6eeb16d53de3%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Adrien

-- 
Please update your bookmarks! We have moved to https://discuss.elastic.co/
--- 
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAO5%3DkAhjZW%2B7BoLqXOk8nEfOvaKrgUroZhbG41BVUDh2bHhEnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to