Erick,
Thanks for the response. After I run the initial query and get a long response
time, if I change the query to remove or add additional query statements, I
find the speed is good.
If I run the modified query after a new searcher has registered, the response
is slow but after the modified query has been completed, the warming query sent
from CuRl is much faster. I assume it is because the document cache has updated
with the documents from the modified query. A large number of our queries work
with the same document set, I am trying to get a warming query to populate the
document cache to be as big as feasible.
Should the firstSearcher and newSearcher warm the document cache?
On Friday, 7 October 2016, 9:31, Erick Erickson <erickerick...@gmail.com>
wrote:
Submitting the exact same query twice will return results from the
queryResultCache. I'm not entirely
sure that the firstSearcher events get put into the cache.
So if you change the query even slighty my guess is that you'll see
response times very close to your
original ones of over a second.
Best,
Erick
On Thu, Oct 6, 2016 at 2:56 PM, Dalton Gooding
<daltonwestco...@yahoo.com.au.invalid> wrote:
> After setting a number of newSearcher and firstSearcher queries, I can see in
> the console logs that the queries are run, but when I run the same query
> against the new searcher (using CuRL), I get a slow response time for the
> first run.
>
> Config:
> <listener event="newSearcher" class="solr.QuerySenderListener"> <arr
>name="queries"> <lst> <str name="fq">DataType_s:Product</str>
> <str name="fq">WebSections_ms:house</str> <str
>name="fq">{!tag=current_group}GroupIds_ms:*</str>
> <str name="facet">true</str> <str
>name="facet.field">BrandID_s</str> <str
>name="facet.query">Price_2_f:[* TO *]</str> <str
>name="facet.query">Price_3_f:[* TO *]</str> <str
>name="facet.query">Price_4_f:[* TO *]</str> <str
>name="facet.query">Price_5_f:[* TO *]</str> <str
>name="facet.query">Price_6_f:[* TO *]</str> <str
>name="facet.query">Price_7_f:[* TO *]</str> <str
>name="facet.query">Price_8_f:[* TO *]</str> <str
>name="facet.mincount">1</str> <str name="facet.method">fc</str>
> <str name="wt">json</str> <str
>name="json.nl">map</str> <str name="q">(title:* OR text:*)</str>
> <str name="start">0</str> <str name="rows">20</str>
> </lst> </arr> </listener>
>
> Console log:
> INFO (searcherExecutor-7-thread-1-processing-x:core1) [ x:core1]
> o.a.s.c.S.Request [core1] webapp=null path=null
> params={facet=true&facet.mincount=1&start=0&facet.query=Price_2_f:[*+TO+*]&facet.query=Price_3_f:[*+TO+*]&facet.query=Price_4_f:[*+TO+*]&facet.query=Price_5_f:[*+TO+*]&facet.query=Price_6_f:[*+TO+*]&facet.query=Price_7_f:[*+TO+*]&facet.query=Price_8_f:[*+TO+*]&event=newSearcher&q=(title:*+OR+text:*)&distrib=false&json.nl=map&facet.field=BrandID_s&wt=json&facet.method=fc&fq=DataType_s:Product&fq=WebSections_ms:house&fq=VisibleOnline_ms:7&fq={!tag%3Dcurrent_group}GroupIds_ms:*&rows=20}
> hits=2549 status=0 QTime=1263
>
>
> If I run the same query after the index has registered I see a QTime of over
> a second, the second time I run the query I see around 80ms. This leads me to
> believe the warming did not occur or the query was not commited to cache on
> start up of the new searcher.
> Can someone please advise on how to use the newSearcher queries to
> effectively warm SolR caches. Should I see an improved response for the first
> time I run the query if the same query has been used as a newSearcher query?
> Cheers,
> Dalton
