Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45537
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.221.191 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;
        b=UBTdcoeQZ2XbuUrU67J5H6Vn9zESE6KbjpwgOuPYjdEN7xq+HgjcxChVAM5sKd1WuC
         uwuhia/G2a9JTKT4Tumb7Z+7NOvsjcjVmzACO/PSp5Gf6dSPpqG31xvZ9BcFheitK4NM
         ++ujV5gwFFe+lBPQbdvM94WSdPPPo03cDtOwY=
MIME-Version: 1.0
In-Reply-To: <4AA760CC.9060203@iki.fi>
References: <99cf22520909081652v29a9ea56q33882849cce3081e@mail.gmail.com>
	 <4AA6F06C.4020008@lerdorf.com> <4AA75C9F.3090605@iki.fi>
	 <4AA75EFF.5040800@zend.com> <4AA760CC.9060203@iki.fi>
Date: Wed, 9 Sep 2009 01:13:36 -0700
Message-ID: <bd9320b30909090113k5431b638v686e0c1359ee6a5e@mail.gmail.com>
To: jani.taskinen@iki.fi
Cc: Stanislav Malyshev <stas@zend.com>, Rasmus Lerdorf <rasmus@lerdorf.com>, 
	dreamcat four <dreamcat4@gmail.com>, internals@lists.php.net, jvlad <dmda@yandex.ru>, 
	Dmitri Dmitrienko <ddmitrie@gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [sapi] PHP-FPM (FastCGI Process Manager), by Andrei 
	Nigmatulin - upstream Y/n?
From: mike503@gmail.com (Michael Shadle)

On Wed, Sep 9, 2009 at 1:01 AM, Jani Taskinen<jani.taskinen@iki.fi> wrote:

> Very good point. And I did consider only merging the _good_ parts of this
> thing. I haven't had time to check the code yet at all (quite busy at work
> right now) but there are some stuff it does we haven't generally considered
> the "job of PHP" before. The list of them is here:
>
> http://php-fpm.org/What_is_PHP-FPM

Current:
Proper termination of errant processes
FastCGI pool configuration, management, proper child recycling
Per-pool php.ini overrides

Future:
Adaptive process spawning (has been in the plans for a while but
Andrei never got a chance to get around to finishing it)
Hopefully some metrics/reporting
Probably changing the configuration file syntax
Per-pool specific php.ini file (basically just php-cgi -c, very simple
addition to add)
(look at the Wishlist page on the wiki...)

Lots of room for improvement. I think it will help with resource
management as well. Right now you have to arbitrarily assign how many
children you want without any real way to measure if it's too many or
too little.

I had suggested this idea at one point - that is adding in only what
is needed from PHP-FPM into PHP core and allowing the management of
those hooks from an external tool developed and maintained separately
(or through API calls) - then a variety of tools could manage the
portions of the FastCGI SAPI that PHP-FPM does to terminate processes,
spawn new children, and do whatever else was patched into PHP, and
keep the management portion which is in charge of launching children,
monitoring them, all that in its own standalone package. I see it as
both allowing for more agile development on the management portion as
it is lacking in a lot of features that we'd like to see (and not have
to wait on PHP core's release cycle to get them in) and also can be
packaged separately in distributions, much like spawn-fcgi is right
now.

Essentially it could be thought of as moving in the direction of
spawn-fcgi (being standalone), just with more robust PHP
functionality.