I'd examine the filter queries used to see whether they make sense as well. You really have to re-tune after you start getting real user queries though as anything you generate won't reflect reality. I'd start _much_ smaller, 512 or 1024 and work _up_ with real data.
Raising the document cache limit is not where I'd start. Given that the docs will eventually be held in MMapDirectory space (i.e. O/S system memory) probably anyway all you're _really_ saving is decompression upon occasion. Best, Erick On Thu, Jul 9, 2015 at 10:58 AM, wwang525 <wwang...@gmail.com> wrote: > Hi, > > The real production requests will not be randomly generated, and a lot of > requests will be repeated. I think the performance will be better due to the > repeated requests. In addition, I am sure the configuration will need to be > adjusted once the application is in production. > > For the time being, I can drop the size of filterCache to 4096 or 2048 since > it is now only 1465 in the stats page. > > I forgot to mention that the size I saw in the stats page for documentCache > is already 16384 after the test, and this is the configured size in > solrconfig.xml. This is why I was asking if I need to raise the number in > the configuration. > > Is there any issue or will there be any performance improvement if I raise > up the size for documentCache? > > Thanks > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/How-to-determine-cache-setting-in-Solr-Search-Instance-tp4216562p4216591.html > Sent from the Solr - User mailing list archive at Nabble.com.
