500 rows can be a lot of rows. A Filter query is a normal query the first time it is run, and cached thereafter. If you do a sequence of different time ranges, it will be slow. So, if you just do a query for each time range, and use the query and filter query caches, they might be faster.
On Sat, Dec 25, 2010 at 7:36 AM, Erick Erickson <erickerick...@gmail.com> wrote: > This sounds like an "XY" problem, see: > http://people.apache.org/~hossman/#xyproblem > > What is the higher-level task you're trying to accomplish? > Some things that do jump out though. > 1> looping is almost always a sub-optimal solution. That's why I'm asking > about > what the higher-level task is. > 2> 500 rows for 10 queries returns 5,000 rows. This seems of little value, > try > reducing the rows to something more manageable, like 10 (or even 5). > 3> if you're trying to get counts for those ranges, consider faceting. > > Best > Erick > > On Sat, Dec 25, 2010 at 9:21 AM, saureen <saureen_ad...@yahoo.co.in> wrote: > >> >> I am using the fq parameter in my solr query for getting the results based >> on >> a date range.so lets say i am searching for a term "iphone" and i want to >> get results from '2010-12-01' to '2010-12-25' ,so fq sets my start date and >> end date,i am doin this in a loop for different time frames and for same >> search keyword.The loop runs 10 to 12 times, >> i.e >> q='iphone' >> fq = date:[2010-12-01T00:00:00Z TO 2010-12-25T00:00:00Z] >> rows=500 >> >> This is taking a long time to process also i am using the sharding based on >> the time range. >> >> Suggest possible steps to optimize the solr search for above scenario. >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/Increase-Search-Speed-for-multiple-solr-request-for-different-time-range-query-tp2144426p2144426.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> > -- Lance Norskog goks...@gmail.com
