Maybe I spoke too soon.
The second and third filter parameter *fq={!cache=false cost=50}ClientID:4*and
*fq={!cache=false cost=150}StartDate:[NOW/DAY TO NOW/DAY+1YEAR] *above are
not getting executed, unless I make it the first parameter. And when it's
the first filter parameter the Qtime goes up to 250ms from 2ms!!
Something I have noticed - Solr always respects only first "q" and "fq"
parameters. Rest of the parameters are not applied at all.
On Thu, Mar 6, 2014 at 11:55 AM, Vijay Kokatnur <kokatnur.vi...@gmail.com>wrote:
> That did the trick Ahmet. The first response was around 200ms, but the
> subsequent queries were around 2-5ms.
>
> I tried this
>
> &q=UserID:AC10263A-E28B-99F9-0012-AAA42DDD9336
> &fq={!cache=false cost=100}Status:Booked
> &fq={!cache=false cost=50}ClientID:4
> &fq={!cache=false cost=50}[NOW/DAY TO NOW/DAY+1YEAR]
>
>
>
> On Thu, Mar 6, 2014 at 11:49 AM, Ahmet Arslan <iori...@yahoo.com> wrote:
>
>> Hi,
>>
>> Did you try with non-cached filter quries before?
>> cached Filter queries are useful when they are re-used. How often do you
>> commit?
>>
>> I thought that we can do something if we disable cache filter queries and
>> manipulate their execution order with cost parameter.
>>
>> What happens with this :
>> &q=UserID:AC10263A-E28B-99F9-0012-AAA42DDD9336
>> &fq={!cache=false cost=100}Status:Booked
>> &fq={!cache=false cost=50}ClientID:4
>>
>> &fq={!cache=false cost=150}StartDate:[NOW/DAY TO NOW/DAY+1YEAR]
>>
>>
>>
>> On Thursday, March 6, 2014 9:15 PM, Vijay Kokatnur <
>> kokatnur.vi...@gmail.com> wrote:
>> Ahmet, I have tried filter queries before to fine tune query performance.
>>
>> However, whenever we use filter queries the response time goes up and
>> remains there. With above change, the response time was consistently
>> around 4-5 secs. We are using the default cache settings.
>>
>> Is there any settings I missed?
>>
>>
>>
>> On Thu, Mar 6, 2014 at 10:44 AM, Ahmet Arslan <iori...@yahoo.com> wrote:
>>
>> > 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!
>> >
>> >
>>
>>
>
