Hi Erick, The way the load test works is that it picks up 5000 queries, splits them according to the number of threads (so if we have 10 threads, it schedules 10 threads - each one sending 500 queries). So it might be possible that the number of queries at a point later in time is greater than the number of queries earlier in time. I'm not very sure about that though. Its a simple Ruby script that starts up threads, calls the search function in each thread, and then waits for each of them to exit.
How many queries per second can we expect Solr to serve, given this kind of hardware? If what you suggest is true, then is it possible that while Solr is serving a query, another query hits it, which increases the response time even further? I'm not sure about it. But yes I can observe the query times going up as I increase the number of threads. Thanks, Regards, On Thu, Mar 11, 2010 at 8:30 PM, Erick Erickson <erickerick...@gmail.com>wrote: > 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 > > > -- - Siddhant
