Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21772
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43E26EFD.9050901@lerdorf.com>
Date: Fri, 03 Feb 2006 09:43:41 +1300
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: Brian Moon <brianm@dealnews.com>
CC: Ilia Alshanetsky <ilia@prohost.org>,
	php internals <internals@lists.php.net>
References: <43E25FEC.3020808@dealnews.com> <43E26C45.9020503@prohost.org> <43E26CF8.5090105@dealnews.com>
In-Reply-To: <43E26CF8.5090105@dealnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP, Apache 2, memory and APC
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Brian Moon wrote:
> Ilia Alshanetsky wrote:
>> Rather then terminating Apache request yourself, you can use universal 
>> Apache configuration directives that allow you to restrict memory 
>> utilization of an Apache process.
> 
> Hmmm, the ones I looked at seemed to prohibit a process from growing 
> above a certain size.  Can you point me to them?  I don't want to 
> prohibit a process from using what it needs (to a point).  I need simply 
> need a child to terminate after it has gone above a certain threshold.
> 
> We found that the norm for our applications was 10-15MB.  Usage above 
> that was the exception.  Some applications (especially when they were 
> generating cache that had gone stale) would need more for a brief 
> period.  I don't want to stop that.

I still think your best bet is to simply allow for the top watermark for 
each of your processes and configure your machines with enough ram to 
handle perhaps a smaller number of processes.  Or fix your code to use 
less if that high watermark is too high.  Killing processes seems like a 
very crude fix here.

-Rasmus