I set the autowarm to 2000, which only takes about two minutes and resolves
my issues.
Thanks for your help!
best,
cloude
On Wed, Mar 25, 2009 at 9:34 AM, Ryan McKinley wrote:
> It looks like the cache is configured big enough, but the autowarm count is
> too big to have good performance.
>
>
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 numbe
- Original Message
> From: Cloude Porteus
> To: solr-user@lucene.apache.org
> Sent: Wednesday, March 25, 2009 11:48:30 AM
> Subject: Re: Snapinstaller + Overlapping onDeckSearchers Problems
>
> Yes, I guess I'm running 40k queries when it starts :) I didn't know that
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
au
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 auto
Hm, I can't quite tell from here, but that is just a warning, so it's not super
problematic at this point.
Could it be that one of your other caches (query cache) is large and lots of
items are copied on searcher flip?
Could it be that your JVM doesn't have large or free enough enough heap? Ca
