tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Initial test of APR on Solaris
Date Sat, 30 Apr 2005 01:38:10 GMT
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
Except for the maxThreads noted below, the Tomcat settings are simply the
default ones.

The results for Http11AprProtocol (with maxThreads = 150):
Concurrency Level:      300
Time taken for tests:   19.281250 seconds
Complete requests:      1000
Failed requests:        0
Write errors:           0
Keep-Alive requests:    1000
Total transferred:      2164000 bytes
HTML transferred:       1934000 bytes
Requests per second:    51.86 [#/sec] (mean)
Time per request:       5784.375 [ms] (mean)
Time per request:       19.281 [ms] (mean, across all concurrent requests)
Transfer rate:          109.59 [Kbytes/sec] received

The results for Http11Protocol (with maxThreads = 350)
Concurrency Level:      300
Time taken for tests:   13.515625 seconds
Complete requests:      1000
Failed requests:        0
Write errors:           0
Keep-Alive requests:    1000
Total transferred:      2164000 bytes
HTML transferred:       1934000 bytes
Requests per second:    73.99 [#/sec] (mean)
Time per request:       4054.688 [ms] (mean)
Time per request:       13.516 [ms] (mean, across all concurrent requests)
Transfer rate:          156.34 [Kbytes/sec] received


Keeping the maxThread count low is the only way I can keep Apr alive at all:
It fails with OutOfMemoryErrors if I give it 350 threads.





This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.



Mime
View raw message