How many outstanding queries do you have at a time? Is it possible that when you start, you have only a few queries executing concurrently but as your test runs you have hundreds?
This really is a question of how your load test is structured. You might get a better sense of how it works if your tester had a limited number of threads running so the max concurrent requests SOLR was serving at once were capped (30, 50, whatever). But no, I wouldn't expect SOLR to bog down the way you're describing just because it was running for a while. HTH Erick On Thu, Mar 11, 2010 at 9:39 AM, Siddhant Goel <siddhantg...@gmail.com>wrote: > Hi everyone, > > I have an index corresponding to ~2.5 million documents. The index size is > 43GB. The configuration of the machine which is running Solr is - Dual > Processor Quad Core Xeon 5430 - 2.66GHz (Harpertown) - 2 x 12MB cache, 8GB > RAM, and 250 GB HDD. > > I'm observing a strange trend in the queries that I send to Solr. The query > times for queries that I send earlier is much lesser than the queries I > send > afterwards. For instance, if I write a script to query solr 5000 times > (with > 5000 distinct queries, most of them containing not more than 3-5 words) > with > 10 threads running in parallel, the average times for queries goes from > ~50ms in the beginning to ~6000ms. Is this expected or is there something > wrong with my configuration. Currently I've configured the queryResultCache > and the documentCache to contain 2048 entries (hit ratios for both is close > to 50%). > > Apart from this, a general question that I want to ask is that is such a > hardware enough for this scenario? I'm aiming at achieving around 20 > queries > per second with the hardware mentioned above. > > Thanks, > > Regards, > > -- > - Siddhant >
