Auto soft commuting that frequently can also dramatically impact
performance. Perhaps not nearly as much as a hard commit, but I would
still consider increasing it.
Also hard commits every 10 seconds at that volume is quite frequent.
I'd consider doing soft commits every 10 seconds and do hard commits
every so many minutes (10 or so?) and tweak from there.
I might also look at your segment merge strategy. With a large number
of small docs, I've seen solr spend a lot of CPU time just merging
segments. You'll probably want to tweak this to be far less aggressive.
Sent from my Windows Phone From: anand.mahajan
Sent: 8/1/2014 9:40 AM
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud Scale Struggle
Oops - my bad - Its autoSoftCommit that is set after every doc and not an
autoCommit.
Following snippet from the solrconfig -
<autoCommit>
<maxTime>10000</maxTime>
<openSearcher>true</openSearcher>
</autoCommit>
<autoSoftCommit>
<maxDocs>1</maxDocs>
</autoSoftCommit>
Shall I increase the autoCommit time as well? But would that mean more RAM
is consumed by all instances running on the box?
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-Scale-Struggle-tp4150592p4150615.html
Sent from the Solr - User mailing list archive at Nabble.com.
