Bill Barker wrote:
I've finally had some time to get the new APR Connector compiled on my
Solaris box, and my initial 'ab' tests seem to show that the Http11Protocol
wins. I can see if I can get some time to do better tests next week.
The test consists of running 'ab' from an XP box like:
ab -n 1000 -c 300 -k http://myserver:8080/tomcat.gif
The results for Http11AprProtocol (with maxThreads = 150):
Concurrency Level: 300
This test is wrong by all means ;)
ab can not put an wait between the keep-alive requests, so basically
you are just choking you network throughput and killing keep-alive cons.
Since it can not put an wait neither the poller can have a chance to
work. When using ab for testing then you should not exceed the
maxThreads, because you have a 300 concurrent users doing requests.
The trick with APR implementation is by presuming that all connected
users will not actually make request concurrently, but let's say
from 1000 connected users, only 100 will be doing requests.
Presuming something like that we can keep the thread count low while
having a large number of connected users.
So to test the performance with ab you should not go over maxThreads.
You can use Peter Lin's test plans for JMeter, that simulates the
real-life scenario, and see how that behaves.
Also an tests the results from Http11Protocol/Http11AprProtocol should
be more or less equal, because like side, no chance for a poller to do
anything.
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
