The core concept behind filter queries is that they cache their results
(list of documents) so that they can filter the main query more efficiently.
But is your query keeps changing, like every minute, the cached results need
to get thrown away and recalculated, every minute.
Can you try hourly resolution or even daily resolution instead?
Or, disable caching for the offending filter query, as in:
Example: q=*:*&fq={!cache=false}inStock:true
Example: q=*:*&fq={!frange l=1 u=4 cache=false}sqrt(popularity)
-- Jack Krupansky
-----Original Message-----
From: sausarkar
Sent: Monday, February 04, 2013 4:48 PM
To: solr-user@lucene.apache.org
Subject: Really bad query performance for date range queries
we are experiencing very bad performance issues with date range queries. We
have configured the date fields as following: Our queries are rounded every
minute:
qt=ads&debugQuery=false&fl=id,StartDt_t110,.......&fq=Status_i110:2&fq=StartDt_t110:{
NOW/MINUTE-150DAYS TO NOW/MINUTE-90DAYS }&start=0&rows=20 Index size - 10
million documents in Solr 4.1 Start of every minute we see the query speed
to be about 10-12 seconds and increases over time. When the query time jump
to more than 10 seconds the linux *load average spikes up to more than 100
*in a 16 CPU machine. Any one has any suggestions how this can be fixed?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Really-bad-query-performance-for-date-range-queries-tp4038435.html
Sent from the Solr - User mailing list archive at Nabble.com.
