the relation between CPU, response time and no of
concurrent requests.
--
View this message in context:
http://www.nabble.com/Tomcat-Concurrent-Requests-tp23815501p23815501.html
Sent from the Tomcat - User mailing list archive at Nabble.com
> From: CrystalCracker [mailto:sudarshan.acha...@gmail.com]
> Given that each request takes 2 seconds on average. Among
> them, some of them
> take less than 500ms, and some take as long as 5 seconds or
> even a little more sometimes.
>
> How many such concurrent request would a tomcat server
> ru
slower and
slower.
--
View this message in context:
http://www.nabble.com/Tomcat-Concurrent-Requests-tp23815501p23816012.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
> From: CrystalCracker [mailto:sudarshan.acha...@gmail.com]
> The 5 seconds calls are all database or webservice calls. So
> they all go to waiting state.
OK. So the bottleneck almost certainly isn't Tomcat.
> I did some load tests using JMeter, but I had problems coming to a
> conclusion with t
CrystalCracker wrote:
Given that each request takes 2 seconds on average. Among them, some of them
take less than 500ms, and some take as long as 5 seconds or even a little
more sometimes.
How many such concurrent request would a tomcat server running on a double
quad-core server handle?
At
> From: David kerber [mailto:dcker...@verizon.net]
> CrystalCracker wrote:
> > How many such concurrent request would a tomcat server
> > running on a double quad-core server handle?
> >
> At least 8 (1 per core), but that's about all you can tell without
> finding where the bottlenecks are.
If I
