Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46336
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.44 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=references:message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:x-mailer:mime-version:subject:date:cc;
        b=uhnRxyGpw61NUjBp0xpJ1DO5Jy3jKcLZj8LjhhjGabvjg/YqmxK9VtJ2gqEu82AX83
         RsTYWylRFZ/INv6iY+86eaBUOJbrVROX+B8jBLF1BDOLVjDMK9cQOJHZ7VHqpJHQfvXr
         FAYtPUV8lhmAOyURhmawHFUh93yt6Vt7kK1mM=
References: <4B190660.2050107@daylessday.org> <bd9320b30912041625w6b726f89pe77982a2415d1a93@mail.gmail.com> <4B1CCA1F.90802@daylessday.org> <bd9320b30912070201j2236af76x7e3811b11c2ff28@mail.gmail.com> <bd9320b30912070335j40fc07cbu1f6a446728c1fecb@mail.gmail.com> <C44B553D4F7642F789EF7C62EE9D4DA5@master37e73933> <3bea96c40912070557t66084de1v6995c2d3a69eea23@mail.gmail.com> <CDE207AF-8147-4BEF-8AFB-91F4683CCB97@gmail.com> <71BBECA1121447DABA6FC42B5A919414@master37e73933>
Message-ID: <D655D7B4-BD27-4451-9686-A74F6FB1DB60@gmail.com>
To: Reinis Rozitis <r@roze.lv>
In-Reply-To: <71BBECA1121447DABA6FC42B5A919414@master37e73933>
Content-Type: text/plain;
	charset=us-ascii;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 7D11)
Date: Mon, 7 Dec 2009 11:13:33 -0800
Cc: php-dev <internals@lists.php.net>
Subject: Re: [PHP-DEV] FPM is available in a separate SVN branch
From: mike503@gmail.com (Michael Shadle)

The problem with running a static amount of processes is trying to  
figure out the right number. Also it is not elastic in any fashion.  
Shared hosts would love the elasticity as it will allow sites to flex  
up and down as needed without giving each individual user more  
processes than they really need

A global max amount of processes or memory consumption metric might be  
useful to throttle the entire daemon from spawning new children.

Sent from my iPhone

On Dec 7, 2009, at 10:26 AM, "Reinis Rozitis" <r@roze.lv> wrote:

>> 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
>
>
>
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>