Re: Strange performance behaviour when concurrent requests are done

I'd guess that what's happening is that you're pegging the CPU with 4 threads, serving up the absolute maximum that the machine will handle. The thing to look at is the throughput rather than avg response time (although that's going down but not as rapidly, which is still a bit puzzling). Usually,

Re: Strange performance behaviour when concurrent requests are done

That's true. But the degradation is so big. If you use lunch concurrent requests to a web app taht doesn't use Solr the time per request won't degradate that much. For me, it looks more like a synchronized is happening somewhere in Solr or Lucene and is causing this.-- View this message in context:

Re: Strange performance behaviour when concurrent requests are done

You have 4 core machine that can execute 4 threads parallel. After 4 threads it will start context switching between threads. -Thanx: Grijesh www.gettinhahead.co.in -- View this message in context: http://lucene.472066.n3.nabble.com/Strange-performance-behaviour-when-concurrent-requests-are

Re: Strange performance behaviour when concurrent requests are done

Any suggestion about this issue?-- View this message in context: http://lucene.472066.n3.nabble.com/Strange-performance-behaviour-when-concurrent-requests-are-done-tp505478p2878758.html Sent from the Solr - User mailing list archive at Nabble.com.