Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46332 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81925 invoked from network); 7 Dec 2009 18:26:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2009 18:26:19 -0000 Authentication-Results: pb1.pair.com smtp.mail=r@roze.lv; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=r@roze.lv; sender-id=pass Received-SPF: pass (pb1.pair.com: domain roze.lv designates 213.175.74.1 as permitted sender) X-PHP-List-Original-Sender: r@roze.lv X-Host-Fingerprint: 213.175.74.1 roze.lv Linux 2.6 Received: from [213.175.74.1] ([213.175.74.1:20188] helo=zeona.lv) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6B/42-31234-9C84D1B4 for ; Mon, 07 Dec 2009 13:26:19 -0500 Received: from master37e73933 (hq.draugiem.lv [81.198.68.1]) by zeona.lv (Postfix) with SMTP id 24925200F399B for ; Mon, 7 Dec 2009 20:26:15 +0200 (EET) Message-ID: <71BBECA1121447DABA6FC42B5A919414@master37e73933> To: "php-dev" References: <4B190660.2050107@daylessday.org> <4B1CCA1F.90802@daylessday.org> <3bea96c40912070557t66084de1v6995c2d3a69eea23@mail.gmail.com> Date: Mon, 7 Dec 2009 20:26:18 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Subject: Re: [PHP-DEV] FPM is available in a separate SVN branch From: r@roze.lv ("Reinis Rozitis") > Correct. Biggest lacking feature. While this maybe a bit out of topic, but just out of curiosity why do you think that adaptive spawning is any good (trying to run more processes in given time period than started) - "stepping" back to how apache operates with its prefork mechanism (iirc there are even people from php-dev community which suggested running apache with start/maxservers identical so there is always constant number of childs (for php processing) to avoid unwanted/unexpected resource consumption? There should be reasons why it was also dropped from the other external process manager lighty/spawn-fcgi and never planned in webservers like nginx .. I would rather want to see one day php (master process) return FCGI_OVERLOADED for the webserver/application to decide what to do next. rr