You simply need to monitor and adjust. Both during testing and in
production because search patterns change over time. Hook up alerting to it
to get notified of high evictions and low cache hit rate so you don't have
to actively look at stats all day.
Here is the graph of Query Cache metrics for http://search-lucene.com/ for
example:
https://apps.sematext.com/spm-reports/s.do?k=eDcirzHG7i
Otis
Solr ElasticSearch Support
http://sematext.com/
On May 2, 2013 5:14 PM, Furkan KAMACI furkankam...@gmail.com wrote:
I read that at wiki:
Sometimes a smaller cache size will help avoid full garbage collections at
the cost of more evictions. Load testing should be used to help determine
proper cache sizes throughout the searching/indexing lifecycle.
Could anybody give me an example scenario of how can I make a test, what
should I do and find a proper cache size at load testing?
