Nigel Hamilton <[EMAIL PROTECTED]> writes:
> Hi,
> I've been trying to setup mod_perl in an Apache/Red Hat
> Linux/mySQL environment for the last couple of weeks.
>
> When running Apache::Registry on production, mod_perl chewed up
> all the available memory (at that stage only 64 Meg) and the system
> started to use swap memory.
>
> So we doubled the memory to 128 Meg and over the next 10 minutes
> of using the site (having restarted the server) we watched as all the
> extra memory was used up and it went back into swap!
>
> So here are some questions:
>
> 1. What is a 'ball-park' figure for mod_perl memory requirements?
http://perl.apache.org/guide
>
> 2. What is the entry level spec for a mod_perl/Apache/Linux server?
http://perl.apache.org/guide
> 3. Should I reduce the number of Apache child processes (currently 10) ...
> to reduce memory consumption?
http://perl.apache.org/guide
> 4. Will mod_perl always ramp up its memory consumption to whatever is
> available?
http://perl.apache.org/guide
> 5. Should we throw money at the problem and just buy more memory?
http://perl.apache.org/guide
> 6. I have not been able to get Apache::DBI to work. Will Apache::DBI
> significantly reduce memory consumption (every script opens a DB handle
> for session checking)?
Put it _first_ in startup.pl.
> Any help, and war stories that you may have would be much
> appreciated ...
http://perl.apache.org/guide
;-)
--
Dave Hodgkinson, http://www.hodgkinson.org
Editor-in-chief, The Highway Star http://www.deep-purple.com
Apache, mod_perl, MySQL, Sybase hired gun for, well, hire
-----------------------------------------------------------------
