Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48086 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26989 invoked from network); 26 Apr 2010 11:18:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Apr 2010 11:18:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=jerome@loyet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=jerome@loyet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain loyet.net from 209.85.218.216 cause and error) X-PHP-List-Original-Sender: jerome@loyet.net X-Host-Fingerprint: 209.85.218.216 mail-bw0-f216.google.com Received: from [209.85.218.216] ([209.85.218.216:41724] helo=mail-bw0-f216.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 37/B4-04231-A9675DB4 for ; Mon, 26 Apr 2010 07:18:51 -0400 Received: by bwz8 with SMTP id 8so11766882bwz.23 for ; Mon, 26 Apr 2010 04:18:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.14.84 with SMTP id f20mr2471041bka.209.1272280727254; Mon, 26 Apr 2010 04:18:47 -0700 (PDT) Received: by 10.204.134.152 with HTTP; Mon, 26 Apr 2010 04:18:47 -0700 (PDT) In-Reply-To: <4BD57525.50803@daylessday.org> References: <4BD54437.2020304@daylessday.org> <4BD54D42.5070400@daylessday.org> <4BD564A9.2060000@daylessday.org> <4BD57525.50803@daylessday.org> Date: Mon, 26 Apr 2010 13:18:47 +0200 Message-ID: To: Antony Dovgal Cc: 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: jerome@loyet.net (=?ISO-8859-1?B?Suly9G1lIExveWV0?=) Le 26 avril 2010 13:12, Antony Dovgal a =E9crit : > On 26.04.2010 14:08, J=E9r=F4me Loyet wrote: >>> What exactly are you going to do? >>> Killing a process is as easy as exit(), no interfacing is needed. >> >> and when threads are used ? You'll kill all threads at once without >> waiting them to finish what they're doing at the time ? > > Let's start from the beginning. > How are you going to detect how much memory a thread consumes? > no ideas