GOMEZ Henri wrote:
Yet Tomcat may only be handling 10-20 requests at the same time.
This seems like a big waste of resources in Tomcat.
From my test with ab, tomcat could handle much more request by
seconds.
from my yesterday bench, you'll see that TC 3.3.1 and 4.0.4
could handle up to 330 req/seconds :
The issue is not how many requests mod_jk/Tomcat can handle.
The issue is that you end up over time with as many AjpConnector
threads being created by Tomcat as you have apache httpd processes
regardless of how many requests are forward on to Tomcat to process.
For example, I have apache running on a server which hosts about 40
websites and handles 10 million page views per month. This requires
at times up to 350 httpd processes to handle peak load. Only one of
those websites uses Tomcat, yet Tomcat ends up spawning 350 AjpConnector
threads. But the load from the one site which forwards some requests
to Tomcat is only 10-15 simultaneous requests. So Tomcat ends up having
350 AjpConnector threads when it only really needs 10-20 threads for
handling the requests which get forwarded to it.
Regards,
Glenn
--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
--
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
