On Thu, Oct 25, 2012 at 4:51 PM, Benoît email@example.com wrote:
I'm in the case where my queries are always filtered by an id group composed
of letters (usually 4)
The list of groups can be big, up to 2000.
I've seen available options from the following page
But i'm not sure to understand them.
Should using options, "execution" : "bool", "_cache": true, improve
If you filter by only one group ID, I think the term filter would be preferable:
Which would be cached by default and the problem is solved
If you need to filter by more than one group ID, I would choose
depending on what kind of queries are run most often. If users
normally choose the same sets of group IDs, I would leave caching
settings to default. Otherwise, I would only change the execution to
"bool", and I wouldn't turn on _cache because that would also cache
the bool filter - and I assume that would change too often - while
individual term filters will be cached by default.
What configuration of indices.cache.filter.size are you using ? I feel 20%
(From this page
Any other tips or recommendations about filter cache tunning ?
I think if you want to fine-tune your cache settings, there's no
getting away from some testing and monitoring. Here's an interesting
blog article that might help:
http://sematext.com/ -- ElasticSearch -- Solr -- Lucene