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.
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a3a0fa7b-49f8-4d78-a520-6eeb16d53de3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.