I've been thinking about the ProxyPass technique for coping with
mod_perl's high memory usage (setup a non-mod_perl httpd that handles all
requests, but ProxyPasses the mod_perl calls to a mod_perl enabled
Apache).
I find that the complexity of this method is more than it should have to
be. For
Squid is the alternative mentioned in the mod_perl_tuning.pod that comes
with mod_perl.
Alternatively, you could try using mod_rewrite, to direct requests for
scripts to a different apache instance (e.g. running on a separate port
or ip). I've never tried this, but it should work.
Squid
On Sun, 17 Jun 2001, Martin Redington wrote:
Squid is the alternative mentioned in the mod_perl_tuning.pod that comes
with mod_perl.
Can Squid read Apache configuration files? On a new site I'm making
(www.shoujoai.com), I have directives in httpd.conf like this:
RewriteRule
- Original Message -
From: Philip Mak [EMAIL PROTECTED]
To: modperl [EMAIL PROTECTED]
Sent: Saturday, June 16, 2001 9:31 PM
Subject: Re: Is ProxyPass the best you can do?
On Sun, 17 Jun 2001, Martin Redington wrote:
Squid is the alternative mentioned in the mod_perl_tuning.pod
Can Squid read Apache configuration files? On a new site I'm making
(www.shoujoai.com), I have directives in httpd.conf like this:
Never used it, I'm afraid ...
Alternatively, you could try using mod_rewrite, to direct requests for
scripts to a different apache instance (e.g. running on a
