On the face of it, it's somewhat unusual to have the cache settings affect indexing performance. What are you seeing and how are you indexing?
Best, Erick On Mon, Jan 13, 2014 at 2:40 PM, P Williams <williams.tricia.l...@gmail.com> wrote: > Hi, > > I've gone through steps for tuning my cache sizes and I'm very happy with > the results of load testing. Unfortunately the cache settings for querying > are not optimal for indexing - and in fact slow it down quite a bit. > > I've made the caches small by default for the indexing stage and then want > to override the values using properties when used for querying. That's > easy enough to do and described in > SolrConfigXml<http://wiki.apache.org/solr/SolrConfigXml> > . > > I store these properties in a solrcore-querying.properties file. When > indexing is complete I could unload the Solr core, move (mv) this file to > conf/solrcore.properties and then load the Solr core and it would pick up > the new properties. The only problem with that is in production I won't > have access to the machine to make changes to the file system. I need to > be able to do this using the Core Admin API. > > I can see that I can specify individual properties with the CREATE command, > for instance property.solr.filterCache.size=2003232. Great! So this is > possible but I still have two questions: > > 1. Is there a way to specify a conf/solrcore-querying.properties file to > the admin/cores handler instead of each property individually? > 2. The same functionality doesn't seem to be available when I call the > RELOAD command. Is this expected behaviour? Should it be? > > Is there a better way? > > Thanks, > Tricia
