Craig O'Brien wrote:
>
> Hello,
>
> Those are similar numbers to what I have been getting on Intel platforms
> with Tomcat3.2.1. You can boost Tomcat to about 90 pages per second using
> ajp13, mod_jk, and reducing the log level to warn rather then info. (of
> course your Servlet code makes a difference) There is actually a bug in the
> logging with Tomcat 3.2.1 -- info actually gives you debug log level.
> According to GOMEZ the ajp13 connector is not fully optimized and mod_jk is
> still unfinished. Apache's performance can be boosted by limiting the
> modules that you use and reducing log levels as well. Interestingly, I was
> testing a servlet which displayed date, session variables, and generated a
> random password and clocked in at about 88 pages per second with mod_jk.
> When I direct connected to Tomcat I was able to get 463 pages per second
> with no errors so there is allot of potential there. I was able to top out
> at 1107 pages per second on that servlet with Resin. Consider your
> bandwidth, of course, 50-60 pages per second can easily overwhelm a T1 line.
> Indeed with a standard 45k+ page you would be lucky to anywhere near 25.
>
Ok, since some questioned my methodology before I've re-run the tests
on the same box (a Sun Ultra 60 2x360 Mhz with Solaris 6 installed). The
same servlet has been used for all this testing. Bandwidth isn't a
problem in our case since I'm pretty sure the two OC-48's and seven
OC-3's can handle pretty much whatever we've got coming in. All tests
were run with 1000 requests and a concurrency of 10.
Apache 1.3.19/Tomcat 3.3M2 with mod_jk in ajp13 usage mode turned out
around 5.37 requests per second with a very very very high IO wait. One
question would be does the mod_jk module open adn close a connection to
the Tomcat engine for every request? That would surely hurt performance.
Talking straight to Tomcat we get 16.11 requests per second. No IO
Wait and it just does it's thing.
iPlanet 4.1SP6 will whip out about 38 requests per second.
The apache build is just a straight build with only the mod_so module
installed along with the default settings. mod_jk was setup with 'warn'
as the logging option even though a 'none' would be nifty.
So it sort of goes back to the original question of is 3.3M2 the way
to go or the 3.2.x family or possibly the 4.x for the best performance?
What about the Apache 2.x tree?
--
Steve Brunton <[EMAIL PROTECTED]> Phone: 404-827-2756
Chief Engineer Enterprise Systems One CNN Center, Atlanta GA
CNN Internet Technologies ICBM: 84W 23' 45" 33N 45' 29"
<*> If at first you don't succeed...blame someone else and seek
counseling <*>
