Nick,
> Why in the WORLD should anyone be serving static html from tomcat through
> the connector from Apache? Working to improve performance of this kind of
> behavior, in my mind, is a total sillyness. A waste of your time. They
> should instead configure Apache to serve html itself and only pass servlet
> and jsp requests to the Container.
I was looking at the second number ( 953/338 - 953 is RPS for static
content served by apache, 338 is servlet served by apache+tomcat ).
I am very happy I'm not the only one believing ( strongly ) that static
content should be handled by Apache - I totally agree.
If you look at the standalone behavior, servlet execution is as fast as
static content on apache ( even faster ). That means mod_jk overhead is
significant - it reduces the speed to 1/3rd.
BTW, some old data ( before tuning the GC in standalone ) showed
ajp13 to be _faster_ than tomcat standalone ( i.e. servlets using
apache+ajp13 were faster than servlets using the standalone connector ),
at that time servlets were running at 1/4 of the speed of static files
served by apache.
Now the standalone runs servlets faster than apache static files ( since
there is no disk access, and the overhead in tomcat has been reduced ),
but the Ajp13 hasn't been tunned ( still uses Strings,
inefficient byte-char conversions, etc).
BTW, I looked a bit this morning - and I'm amazed. Dan, you did a great
job with the comments. It would be great if you could do something like
that in other areas of tomcat.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
