Sean Kelly wrote:
> Yes, I am also using CGI.pm and thought this was a bit of a hog
> ... I am planning to finish off my cut-down version of CGI.pm to handle
> just the CGI I need in an OO sense (this is a very small amount). I will
> be monitoring improvements when this goes into devel.
>
> To my knowledge I am not using IO:: modules (and /perl-status?inc
> is not showing any).
>
As long as you are loading CGI in your PerlRequire startup.pl
with the compile option, CGI should not be hurting you as
its loaded in the parent httpd. You can also precompile
your CGI scripts with Apache::RegistryLoader for a big win
in processor speed and memory. Finally, I would recommend
running a reverse mod_proxy server even on the same box port 80
to better leverage your heavy mod_perl processes. These things
are all documented in the guide.
To see how much memory impact these things are having, you
might have to look at total RAM free before and after server
stop/start. Also, do hammer your server with ab for a load
test to see how your MaxClient settings hold up.
-- Joshua
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks >> free web link monitoring Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
