Resolve differences in the autowarmCount attribute of the queryResultCache element [#1611678]

The autowarm attribute of the following configuration differs between Apache Solr Search Integration and Search API.

   <!-- queryResultCache caches results of searches - ordered lists of
         document ids (DocList) based on a query, a sort, and the range
         of documents requested.  -->
    <queryResultCache
      class="solr.LRUCache"
      size="512"
      initialSize="512"
      autowarmCount="32"/>

Apache Solr Search Integration sets a value of 32, whereas Search API uses the default of 0.

Comment	File	Size	Author
#1	1611678-1.patch	408 bytes	Nick_vh

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Nick_vh

he/him

Ghent

CreditAttribution: Nick_vh commented 1 June 2012 at 12:11

File	Size
1611678-1.patch	408 bytes

The number of entries to prepopulate from an old cache.

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.

I vote to keep the the 32 value. It does not harm and it improves caching results (afaik)