You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2007/08/11 03:11:09 UTC

[Solr Wiki] Update of "SolrPerformanceFactors" by paulsundling

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The following page has been changed by paulsundling:
http://wiki.apache.org/solr/SolrPerformanceFactors

The comment on the change is:
add link that talks about optimizing/file descriptors.

------------------------------------------------------------------------------
     * Auto-warming time will grow since it's normally dependent on doing searches. 
     * The first distribution after an optimization will take longer than subsequent ones. See [:CollectionDistribution:Collection Distribution] for more information.
  
+ Since optimizing an index saves all the segments in an index (about 7 files per segment) into a single segment, optimizing an index helps avoid the "too many open files" problem, i.e. running out of file descriptors, which is mentioned in an [http://www.onjava.com/pub/a/onjava/2003/03/05/lucene.html#indexing_speed ONJava Article].
+ 
  == Updates and Commit Frequency Tradeoffs ==
  
  If slaves receive new collections too frequently their performance will suffer. In order to avoid this type of degradation you must understand how a  slave receives a collection update so that you can know how to best adjust the relevant parameters (number/frequency of commits, snappullers, and autowarming/autocount) so that new collections do not get installed on slaves too frequently.