[Solr Wiki] Update of "SolrCaching" by HossMan

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

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

The "SolrCaching" page has been changed by HossMan.
The comment on this change is: http://mail-archives.apache.org/mod_mbox/lucene-dev/201005.mbox/%3Calpine.DEB.1.10.1005251052040.24672@radix.cryptio.net%3E.
http://wiki.apache.org/solr/SolrCaching?action=diff&rev1=18&rev2=19

--------------------------------------------------

  
  When a new searcher is opened, its caches may be prepopulated or "autowarmed" with cached object from caches in the old searcher. autowarmCount is the number of cached items that will be regenerated in the new searcher. You will proably want to base the autowarmCount setting on how long it takes to autowarm. You must consider the trade-off — time-to-autowarm versus how warm (i.e., autowarmCount) you want the cache to be. The autowarm parameter is set for the caches in solrconfig.xml.
  
- <!> [[Solr1.5]] autowarmCount can now be specified as a percentage (ie: "90%") which will be evaluated relative the number of items in the existing cache.  This can be an advantageous setting in an instance of Solr where you don't expect any search traffic (ie a master), but you want some caches so that if it does take on traffic it won't be too overloaded.  Once the traffic dies down, subsequent commits will gradually decrease the number of items being warmed. 
+ <!> [[Solr4.0]] autowarmCount can now be specified as a percentage (ie: "90%") which will be evaluated relative the number of items in the existing cache.  This can be an advantageous setting in an instance of Solr where you don't expect any search traffic (ie a master), but you want some caches so that if it does take on traffic it won't be too overloaded.  Once the traffic dies down, subsequent commits will gradually decrease the number of items being warmed. 
  
  == minSize (optional) ==
  Only applicable for `FastLRUCache` . After the cache reaches its size, the cache tries to bring it down to the `minSize`. The default value is `0.9 * size` .