Shawn,
I changed the autoSoftCommit value to 15000 (15 sec).
My index size is pretty small ~4GB and its running on a SSD drive with ~100 GB
space on it.
Now I see the warn message every 15 seconds.
The caches I think are minimal
<filterCache class="solr.FastLRUCache" size="512" initialSize="512"
autowarmCount="0"/>
<queryResultCache class="solr.LRUCache" size="512"
initialSize="512" autowarmCount="0"/>
<documentCache class="solr.LRUCache" size="512"
initialSize="512" autowarmCount="0"/>
<queryResultMaxDocsCached>200</queryResultMaxDocsCached>
I think still something is going on. I mean 15s on SSD drives is a long time to
handle a 4GB index.
Thanks,
Rishi.
-----Original Message-----
From: Shawn Heisey <s...@elyograg.org>
To: solr-user <solr-user@lucene.apache.org>
Sent: Fri, Mar 28, 2014 3:28 pm
Subject: Re: SOLR Cloud 4.6 - PERFORMANCE WARNING: Overlapping onDeckSearchers=2
On 3/28/2014 1:03 PM, Rishi Easwaran wrote:
> I thought auto soft commit was for NRT search (shouldn't it be optimized for
search performance), if i have to wait 10 mins how is it NRT? or am I missing
something?
You are correct, but once a second is REALLY often. If the rest of your
config is not set up properly, that's far too frequent. With commits
happening once a second, they must complete in less than a second, and
that can be difficult to achieve.
A typical extreme NRT config requires small (or disabled) Solr caches,
no cache autowarming, and enough free RAM (not allocated to programs) to
cache all of the index data on the server. If the index is very big, it
may not be possible to get the commit time below one second, so you may
need to go with something like 10 to 60 seconds.
Thanks,
Shawn
