It looks like the cache is configured big enough, but the autowarm
count is too big to have good performance.
Try something smaller and see if that fixes both problems. I imagine
even just warming the most recent 100 queries would precache the most
important ones, but try some higher numbers and see if the performance
is acceptable.
for the filterCache and queryCache, autowarm queries the new index and
caches the results.
On Mar 25, 2009, at 11:48 AM, Cloude Porteus wrote:
Yes, I guess I'm running 40k queries when it starts :) I didn't know
that
each count was equal to a query. I thought it was just copying the
cache
entries from the previous searcher, but I guess that wouldn't
include new
entries. I set it to the size of our filterCache. What should I set
the the
autowarmCount to if I want to try and fill up the caches?
lookups : 8720372
hits : 8676170
hitratio : 0.99
inserts : 44551
evictions : 0
size : 44417
cumulative_lookups : 8720372
cumulative_hits : 8676170
cumulative_hitratio : 0.99
cumulative_inserts : 44551
cumulative_evictions : 0
best,
cloude
On Wed, Mar 25, 2009 at 8:38 AM, Ryan McKinley <ryan...@gmail.com>
wrote:
I don't understand why this sometimes takes two minutes between
the start
commit & /update and sometimes takes 20 minutes? One of our caches
has
about
~40,000 items, but I can't imagine it taking 20 minutes to
autowarm a
searcher.
What do your cache configs look like?
How big is the autowarm count?
If you have:
<queryResultCache
class="solr.LRUCache"
size="512"
initialSize="512"
autowarmCount="32"/>
that will run 32 queries when solr starts. Are you running 40K
queries
when it starts?
ryan
--
VP of Product Development
Instructables.com
http://www.instructables.com/member/lebowski
