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] Update of "SolrCaching" by GrantIngersoll
Date Fri, 11 Feb 2011 23:13:26 GMT
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 GrantIngersoll.
http://wiki.apache.org/solr/SolrCaching?action=diff&rev1=23&rev2=24

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

  Lucene has a low level "FieldCache" which is used for sorting (and in some cases faceting).
 This cache is not managed by Solr it has no configuration options and cannot be autowarmed
-- it is initialized the first time it is used for each Searcher.
  
  See below for ways you can "explicitly warm" the FieldCache using newSearcher and firstSearcher
event listeners.
+ 
+ Solr's stats.jsp page (Admin->Statistics) provides some insight into the FieldCache via
a few entries:
+ 
+  1. entries_count -- The number of items in the FieldCache
+  1. insanity_count -- the number of insane instances
+  1. insanity_[i] -- For each insanity item, list out what type of insanity is happening.
 See http://lucene.apache.org/java/3_0_2/api/core/org/apache/lucene/util/FieldCacheSanityChecker.InsanityType.html
or other versions for more information.
+ 
+ The term insanity is meant to imply that something is going wrong with how the system is
invoking or using the FieldCache via sorting, function queries or something else.  This can
be quite subtle, so it is probably best to ask on the user mailing list and provide information
about how you are sorting, faceting, querying, etc.  Not also, that just because there is
some insanity happening, doesn't mean there is anything that needs to be fixed immediately.
  
  = Other Cache-relevant Settings =
  == newSearcher and firstSearcher Event Listeners ==

Mime
View raw message