Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47957 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29450 invoked from network); 15 Apr 2010 08:36:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2010 08:36:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 89.208.40.236 mail.daylessday.org Linux 2.6 Received: from [89.208.40.236] ([89.208.40.236:58146] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/E6-20494-020D6CB4 for ; Thu, 15 Apr 2010 04:36:49 -0400 Received: from [192.168.3.218] (unknown [212.42.62.198]) by daylessday.org (Postfix) with ESMTPSA id 06B59BFA08B; Thu, 15 Apr 2010 12:36:45 +0400 (MSD) Message-ID: <4BC6D01C.30407@daylessday.org> Date: Thu, 15 Apr 2010 12:36:44 +0400 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100228 SUSE/3.0.3-1.1.1 Thunderbird/3.0.3 MIME-Version: 1.0 To: =?UTF-8?B?SsOpcsO0bWUgTG95ZXQ=?= CC: internals@lists.php.net References: <4BC6CAE6.5020605@daylessday.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] One suggestion to PHP-FPM From: tony@daylessday.org (Antony Dovgal) On 15.04.2010 12:23, Jérôme Loyet wrote: > 2010/4/15 Antony Dovgal : >> On 06.04.2010 11:11, 滕路遥 wrote: >>> So I suggest that if we could add a config option to PHP-FPM, so that >>> PHP-FPM could just kill a PHP process if it consumes too much memory >>> (say more than 256M). >> >> I personally don't think this belongs to any SAPI. >> How about adding another ini option to PECL/memtrack to not just throw a warning, >> but terminate the process when it hits some limit? > > In fork processes it could be great but when dealing with threads it won't work Adding this to FPM won't help anyway - FPM doesn't use threads. -- Wbr, Antony Dovgal --- http://pinba.org - realtime statistics for PHP