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 StevenParkes: http://wiki.apache.org/solr/SolrPerformanceFactors ------------------------------------------------------------------------------ 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. - 1. A snapshot of the collection is taken every time a client runs a commit, or an optimization is run depending on weather `postCommit` or `postOptimize` hooks are used on the master. + 1. A snapshot of the collection is taken every time a client runs a commit, or an optimization is run depending on whether `postCommit` or `postOptimize` hooks are used on the master. 1. Snappullers on the slaves running on a cron'd basis check the master for new snapshots. If the snappullers find a new collection version the slaves pull it down and snapinstall it. 1. Every time a new index searcher is opened, some autowarming of the cache occurs before Solr hands queries over to that version of the collection. It is crucial to individual query latency that queries have warmed caches.
