I'm looking at how to best avoid downtime during a code upgrade, as we often
do spot releases of critical code fixes and we're getting to the usage level
that I don't want to interrupt service to deploy that code. At the same
time, I want to avoid running 200 stat()'s per request for all of the loaded
modules.
We're presently running in this configuration:
Apache 1.3.22
static mod_perl 1.26
Apache::StatINC <--Want to get rid of it.
PerlFreshRestart OFF
I see three options open to me:
1. static mod_perl w/ PerlFreshRestart
Reloads %INC.
downside: Heresay claims historical instablity.
2. dynamic mod_perl
Tears down & cleans up Perl interpreter on graceful restart.
downside: Heresay claims historical instablity.
3. static mod_perl w/ Apache::StatInc
Runs many stat()'s per request.
downside: Runs many stat()'s per request.
Aside from the historical instability, the second option strikes me as the
cleanest and most robust. How has the current stability of these mechanisms?
Is it enterprise-worthy? I'm variously running on RedHat Linux 7.0 and 7.1.
--
Gordon Henriksen
IT & Engineering
ICLUBcentral Inc.
[EMAIL PROTECTED]
