hi,
i'd disagree on this - imagine you have a webserver with reasonable load and
99.9% of php page requests use max 10mb ram. you have 1% that use 100mb ram.
then it not a good idea to upgrade to 1g ram just for these 0.1% since each
httpd process will hold 100mb ram after certain time (the 0.1% will spread
on all httpd processes)
on the other side getting and returning ram to the system is not a fast
thing and should be avoided. most common solution is to tell the memory
cache how much ram to held. or preset it at compile time.
i see that my most loaded system (most complex scripts) uses about 10m per
process.
b.
> Seems to me like it would be a lot easier just to add more RAM. $89 for
> 256M these days. RAM is cheap.
>
> > That is what we are doing now. We have it at 5. Any higher and we are
> > running out. There is only 128MB of RAM in our machine. I am
considering
> > switching to CGI PHP just to eliviate this problem. Of course, that
sucks.
> >
> > > > Yes, yes, I agree ! But this is the problem ! Unfortunatelly "memory
> > > > hungry script" happens from time to time and there's no chance to
prevent
> > > > httpd processes from keeping memory (which is not used again in most
> > > > cases). Maybe it is not a problem for you, but it is for us.
> > >
> > > A quick fix would be to set your MaxRequestsPerChild to a lower value.
> > >
--
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]
