Might I add ...
As I came to this a bit late, may I suggest some "conservative" numbers
to work up from:
- Assume each httpd with mod_perl will eat up 6mb of private memory if
you set max-requests per child fairly low (e.g. 35).
- Take your real memory. Subtract 32Mb. Divide remaining memory by 7mb
(to give you a bit of breathing room. That number is a SWAG at a the max
clients upper bound.
- Top is useful, but your key tool is "vmstat 5 5" or similar. Look for
"pi" (page-in) and "po" (page out) values greater than 0 (ignore the
first line of the output) when your web server has been running for at
least 10-30 minutes during your peak busy period. If the po value is
ANYTHING BUT 0 you stealing pages from running processes; if the pi
value is nonzero except when starting new processes (e.g. httpd's,) you
have a memory overcommitment. Top will help you but vmstat will tell you
EXACTLY if you are paging. Incidentally, once you really are comfortable
with your system's performance, a pi of 1-3 pages/second is OK.
- If you are running other things on the server (e.g. a database server,
CORBA client, etc.) that runs its OWN processes, then your mileage may
vary, but the pi/po values above are your key clue to memory
overcommitments.
good luck.
Joshua Chamas wrote:
>
> > praveen wrote:
> >
> > Sir,
> >
> > We have recently installed our server having the configuration as- Linux ,
>modperl,apache, samba.
> > The problem we are facing is after few minutes of working server hangs giving the
>error message as "out of memory" for all the above configuration.
> > Please help me as soon as possible
> >
> > Thanks
> > Praveen
> > E-mail address - [EMAIL PROTECTED]
> >
>
> You are probably running too many mod_perl processes.
>
> Set the MaxClients lower. Also, set your MaxRequestsPerChild
> lower (100-1000), so the httpds don't bloat too much over
> time. If you need more web processes feeding clients
> consider putting a thin reverse proxy in front, like
> apache w/proxy or squid.
>
> Get a program like top, and make sure you keep some
> RAM free and that you are swapping minimally.
>
> There's a chance that if you are running your web server
> with DSO, not statically compiled, that you are getting
> this error because of the DSO quirkiness. This isn't an
> RPM is it ?
>
> -- Joshua
> _________________________________________________________________
> Joshua Chamas Chamas Enterprises Inc.
> NODEWORKS >> free web link monitoring Huntington Beach, CA USA
> http://www.nodeworks.com 1-714-625-4051
--
Daemeon Reiydelle
Systems Engineer, Anthropomorphics Inc.
[EMAIL PROTECTED]
