Hi,
Since your range query has NOW in it, it won't be cached meaningfully.
http://solr.pl/en/2012/03/05/use-of-cachefalse-and-cost-parameters/
This is untested but can you try this?
&q=UserID:AC10263A-E28B-99F9-0012-AAA42DDD9336
&fq=Status:Booked
&fq=ClientID:4
&fq={!cache=false cost=150}StartDate:[NOW/DAY TO NOW/DAY+1YEAR]
On Thursday, March 6, 2014 8:29 PM, Vijay Kokatnur <kokatnur.vi...@gmail.com>
wrote:
I am working with date range query that is not giving me faster response
times. After modifying date range construct after reading several forums,
response time now is around 200ms, down from 2-3secs.
However, I was wondering if there still some way to improve upon it as
queries without date range have around 2-10ms latency,
Query : To look up upcoming booked trips for a user whenever he logs in to
the app-
q=UserID:AC10263A-E28B-99F9-0012-AAA42DDD9336 AND Status:Booked
ANDClientID:4 AND StartDate:[NOW/DAY TO NOW/DAY+1YEAR]
Date configuration in Schema :
<field name="StartDate" type="tdate" indexed="true" stored="true" />
<fieldType name="tdate" class="solr.TrieDateField" precisionStep="6"
positionIncrementGap="0"/>
Appreciate any inputs.
Thanks!
