Would we expect anything markedly different with Apache 2 worker rather
than prefork? This would seem a bit more of an apples-to-apples
comparison (i.e. comparing multi-threaded low-process count servers).
Also how many simultaneous workers (threads/processes/whatever) were
allowewd in each case?
[I stopped using prefork on all platforms when moving to Apache 2.]
--
Jess Holle
Mladen Turk wrote:
Hi,
Here are the brief results for Tomcat HEAD:
Server Threads Pause (ms) Error(%) Rate (req/sec)
Apache2.0.49 500 1000 1.74 124.2
Http11Protocol 500 1000 0.20 139.5
Http11AprProtocol 500 1000 0.00 266.9
Tests has been run on SLES9/64-Bit/Java-1.5.0_02-b09
Client was WINXP/SP2 running JMeter and Peter Lin's test plans.
Those tests simulate 500 concurrent users connecting to a
150 maxClient server. The connection is keep-alive with
1 second delay between the requests.
So our JNI/APR http connectors is almost twice faster then
both Tomcat standard http connector and Apache2/prefork.
What is more important is that the error number is zero,
meaning there were no refused connections, because of
keepalive connection poller.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
