On Fri, 29 Jun 2001, Pier P. Fumagalli wrote:
> It's _VERY_MUCH_ a work in progress... I am NOT DEFINITELY comfortable with
> its code, and I'm the one who wrote it, soooooo :) :) :)
heh.
> All I can say is that right now I'm so happy to see that few people gave me
> feedback on that piece of code that I thought nobody really cared about,
> somehow I got a reason to go on developing it...
i care very much about mod_webapp. er, well, to be more clear, i care very
much about having an apache-tomcat connector module that doesn't require
me to put the same configuration data in two completely different places.
i presume mod_webapp is the only component trying to tackle that job, but
if there are others, i'm all ears.
anyway, i just ran some benchmarks and mod_webapp hasn't choked once, but
it is significantly slower than tomcat standalone. for 100 requests at
concurrency 10, it typically takes apache+tomcat 45 seconds, while tomcat
gets through at about 30 seconds. logging could account for some of this,
as mod_webapp and/or the java warp connector seem to be very verbose.
nonetheless, do others experience this?
oh, also, i ran into an OutOfMemory error when i really slammed the
server. i hadn't experienced that before with tomcat standalone. could
there be a memory leak in the WarpConnector code? has anyone else run into
this?
- donald
