Thanks Yonik,

I'm cooking up some static warming queries right now, based upon our commonly 
issued queries.  I've already been noticing occasional long running queries.  
Our web farm times out a search after twenty seconds and issues an exception.  
I see a few of these every day and am trying to combat them with better warm up 
queries.  My current static warm up queries are too simple I suspect.  They 
don't replicate any of our typically issued filter queries nor function queries.

Thanks
Robi

-----Original Message-----
From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley
Sent: Tuesday, January 29, 2013 2:46 PM
To: solr-user@lucene.apache.org
Subject: Re: queryResultCache *very* low hit ratio

One other thing that some auto-warming of the query result cache can achieve is 
loading FieldCache entries for sorting / function queries so real user queries 
don't experience increased latency.  If you remove all auto-warming of the 
query result cache, you may want to add static warming entries for these fields.

-Yonik
http://lucidworks.com


On Tue, Jan 29, 2013 at 3:36 PM, Petersen, Robert <rober...@buy.com> wrote:
> Hi solr users,
>
> My queryResultCache hitratio has been trending down lately and is now at 
> 0.01%, and also it's warmup time was almost a minute.  I have lowered the 
> autowarm count dramatically since there are no hits anyway.  I also wanted to 
> lower my autowarm counts across the board because I am about to expand the 
> warmup queries in my newSearcher config section.  Would I be better just 
> turning off this cache completely?  I don't really want to increase its size 
> because I've found that by keeping my cache sizes limited keeps me from 
> getting OOM exceptions across my slave farm.
>
> Thanks,
>
> Robert (Robi) Petersen
> Senior Software Engineer
> Search Department
>


Reply via email to