On the surface, this doesn't seem right. Your corpus isn't very large and it sounds like you have some significant hardware supporting it. I'm guessing you have some other issues here like; - inappropriate memory allocation - too-frequent commits - too many queries for your hardware - indexing to the same machine
I'd attach a memory profiler to the app and watch that, also are you sure it's the fq? You should be able to just submit various forms of the query by hand. You may need to throw more hardware at it. Best Erick On Mon, Feb 4, 2013 at 6:14 PM, sausarkar <sausar...@ebay.com> wrote: > Unfortunately we need data by minute we cannot go hour, is there an option > for 3 minutes or 5 minutes? something is like NOW/3MIN? > > I am also noticing when I generating around 110 queries per second (date > range ones) after sometime solr does not respond and just freezes. Is there > a way to cure this? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Really-bad-query-performance-for-date-range-queries-tp4038435p4038455.html > Sent from the Solr - User mailing list archive at Nabble.com. >
