Hi, My first suggestion is to not commit so often. Use autocommit with maxTime higher than a minute and openSearcher false. Turn on autoSoftCommit and set that higher than 10 seconds if you can handle it. Use a higher mergeFactor than 10, like 35 for example.
After that you're probably going to have to do some profiling to see what the bottleneck is. Iostat helps a lot with that. Michael Della Bitta Applications Developer o: +1 646 532 3062 | c: +1 917 477 7906 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions <https://twitter.com/Appinions> | g+: plus.google.com/appinions w: appinions.com <http://www.appinions.com/> On Wed, Jun 12, 2013 at 10:50 AM, adfel70 <adfe...@gmail.com> wrote: > Hi, > We have a multi-sharded and multi-replicated collection (solr 4.3). > > When we perform massive indexing (adding 5 million records with 5k bulks, > commit after each bulk), the search performance is degrades a lot (1 sec > query can turn to 4 sec query). > > Any rule of thumb regarding best configuration for this kind of a scenario? > > thanks. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Any-inputs-regarding-massive-indexing-to-a-cluster-and-search-performance-tp4069955.html > Sent from the Solr - User mailing list archive at Nabble.com. >
