Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48081
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=UXJxbWXFE9rVA8XD7weFYPhknRI589NHSFpB1kQJvWz64gapTKLQQRrsbPAktKXjtt
         RJ+Ph2s0WL3/wqUfLb7RHSuTnhztVnKYNVNUdSeag5P+GeeCOxPF8ApDCdqk6pMFiqKg
         Geec0LAuTm82kUJzjx64xhj78HEqZoyD8NC1s=
MIME-Version: 1.0
In-Reply-To: <4BD54D42.5070400@daylessday.org>
References: <j2g7b32197c1004060011n5b78f062kf05bde7d0b2b9993@mail.gmail.com>
	 <p2z3bea96c41004140029pe2e65660rb15c56e1040ca6f6@mail.gmail.com>
	 <j2n3bea96c41004140201ia1cffc4fr1c191a343af73931@mail.gmail.com>
	 <4BC58D10.4050609@lerdorf.com>
	 <q2l3bea96c41004231525t10d5e282w8ac6ff58129ce8c4@mail.gmail.com>
	 <p2h7b32197c1004251902yca622d25y361a1a9b3fab9ef@mail.gmail.com>
	 <u2n3bea96c41004252358la9bfc7f1w46c5e428a3a3bd18@mail.gmail.com>
	 <4BD54437.2020304@daylessday.org>
	 <q2j3bea96c41004260115iac33d39fnb7d303794997acf5@mail.gmail.com>
	 <4BD54D42.5070400@daylessday.org>
Date: Mon, 26 Apr 2010 10:23:32 +0200
Message-ID: <y2hfe05d1541004260123g582e32e8z401c4293761b70e4@mail.gmail.com>
To: Antony Dovgal <tony@daylessday.org>
Cc: =?ISO-8859-1?B?Suly9G1lIExveWV0?= <jerome@loyet.net>, 
	internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] One suggestion to PHP-FPM
From: pierre.php@gmail.com (Pierre Joye)

hi,

I agree with Tony. Such features should be part of memtrack or the
engine but not SAPI specific.

Cheers,

2010/4/26 Antony Dovgal <tony@daylessday.org>:
> On 26.04.2010 12:15, J=E9r=F4me Loyet wrote:
>> 2010/4/26 Antony Dovgal <tony@daylessday.org>:
>>> On 26.04.2010 10:58, J=E9r=F4me Loyet wrote:
>>>> Le 26 avril 2010 04:02, looyao teng <tly.phpfans@gmail.com> a =E9crit =
:
>>>>> in linux, read the /proc/self(pid)/status, =A0and the VmRSS(real memo=
ry usage)
>>>>> or VmSize(virtual memory usage) =A0is the the memory usage of =A0the =
current
>>>>> process.
>>>>
>>>> in fact I was looking of a cleaner way to do it.
>>>
>>> PECL/memtrack does it already.
>>> I still don't get why do you want to duplicate it in FPM?
>>
>> I think the goal is not the same. PELC/memtrack produce a warning if
>> memory is over the soft limit and stops execution if it's over the
>> hard limit.
>
> You can always add another limit and another action.
>
>> Moreover, it checks only the memory allocated by the Zend
>> Stack.
>
> Nope.
>
>> The goal here is to mesure memory usage after each request and kill
>> the process if it's larger than the limit. We don't wan't to limit
>> each process but we want to check it's been free'd correctly
>>
>> It's easy to do when checking the Zend Stack Size (ZSS ?) but it's not
>> the same if you want to check also memory allocation which have
>> bypassed the ZSS.
>
> That's why memtrack uses mallinfo().

--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org