Thank you all for your fast replies,
Changing photo_id:* to boolean has_photo field via transformer, when
importing data, *fixed my problems*; reducing query times to *30~ ms*.
I'll try to optimize furthermore by your advices on filter query usage and
int=>tint (will search it first) transform.
O
: &q=photo_id:* AND gender:true AND country:MALAWI AND online:false
photo_id:* does not mean what you probably think it means. you most
likely want photo_id:[* TO *] given your current schema, but i would
recommend adding a new "has_photo" boolean field and using that instead.
thta alone shou
more
direct answer...
JRJ
-Original Message-
From: Yusuf Karakaya [mailto:karakaya...@gmail.com]
Sent: Wednesday, September 14, 2011 11:31 AM
To: solr-user@lucene.apache.org
Subject: Re: Performance troubles with solr
I tried moving age query from filter query to normal query but no
ednesday, September 14, 2011 9:54 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Performance troubles with solr
>
> Thank you for your reply.
> I tried to give most of the information i can but obviously i missed some.
> 1. Just what does your "test script" do? Is it
-user@lucene.apache.org
Subject: Re: Performance troubles with solr
Thank you for your reply.
I tried to give most of the information i can but obviously i missed some.
1. Just what does your "test script" do? Is it doing updates, or just
queries of the sort you mentioned below?
Test scri
Thank you for your reply.
I tried to give most of the information i can but obviously i missed some.
1. Just what does your "test script" do? Is it doing updates, or just
queries of the sort you mentioned below?
Test script only sends random queries.
2. If the test script is doing updates, how
I think folks are going to need a *lot* more information. Particularly
1. Just what does your "test script" do? Is it doing updates, or just
queries of the sort you mentioned below?
2. If the test script is doing updates, how are those updates being fed to
Solr?
3. What version of Solr
