MaxRequestsPerChild is perfectly safe, and I always believe in setting it.
Keep in mind that if you compile all modules into apache statically, it takes
up far more base mem per process. If you use all DSO's, you can
significantly reduce memory usage. To find out what's in use on RH7
cat /proc/<pid>/maps of an apache child.
You can also reduce the KeepAlive timeout value to help-out.
Jason
>
>
>
> ----- Original Message -----
> From: "Rasmus Lerdorf" <[EMAIL PROTECTED]>
> To: "Filip Sielimowicz" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, January 29, 2001 7:51 AM
> Subject: Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.
>
>
> > On Mon, 29 Jan 2001, Filip Sielimowicz wrote:
> >
> > > > A quick fix would be to set your MaxRequestsPerChild to a lower value.
> > >
> > > Have you ever tried to measure the time of killing and
> > > starting httpd process ? You can see that with a bare human eye.
> >
> > Sure. But that isn't something that happens on an actual request, so an
> > end user isn't going to see that.
> >
> > -Rasmus
> >
> >
> > --
> > PHP Development Mailing List <http://www.php.net/>
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > To contact the list administrators, e-mail: [EMAIL PROTECTED]
> >
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
