lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Trivial Update of "SolrCaching" by YonikSeeley
Date Mon, 24 Nov 2008 04:39:01 GMT
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 YonikSeeley:
http://wiki.apache.org/solr/SolrCaching

------------------------------------------------------------------------------
  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.
  
  == minSize (optional) ==
- Only applicable for `FastLRUCache` . After the cache reaches its size, the cache tries to
bring it down to the `minSize`. If not mentioned the default value will be `0.9 * size` .

+ 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` . 
  
  == acceptableSize (optional) ==
- Only applicable for `FastLRUCache` . When the cache removes old entries , it targets to
achieve the `minSize` . If not possible it atleast tries to bring it down to `acceptableSize`.If
not mentioned the default value will be `0.95 * size` . 
+ Only applicable for `FastLRUCache` . When the cache removes old entries , it targets to
achieve the `minSize`. If not possible it at least tries to bring it down to `acceptableSize`.
 The default value is `0.95 * size`. 
  
  
  == cleanupThread (optional) ==
- Only applicable for `FastLRUCache` . Default is set to false. If set to true , the cleanup
will be run in a dedicated separate thread. When the cleanup is fired (i.e when cache size
reaches upper water mark) the particular request can take very long time if this is not set
to true.
+ Only applicable for `FastLRUCache`. Default is set to false. If set to true, the cleanup
will be run in a dedicated separate thread.  Consider setting this to true for very large
cache sizes, as the cache cleanup (triggered when the cache size reaches the upper water mark)
can take some time.
  
  = Types of Caches and Example Configuration =
  

Mime
View raw message