Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49675
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 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=l9T4Tpj17zWVyGuson24wTYwcv7L0iFo/mBwzxyECBV4j0HEMe+c9kn7eAz6EMmFI7
         aXe4hr0e5znSx1b3oNpVnuvV9SOTy5mrJ7rH807i3s9igGhMM1GKeVtDZW6vZhk2pJ6r
         2dPjJL3lw6n8OLZUxeZWtm0q8Na8ryjl+Ju6Q=
MIME-Version: 1.0
In-Reply-To: <4C910E9C.7040004@lerdorf.com>
References: <AANLkTinF=ZctV7e5jzGERJ_mZYn4R75fq1szsXJ4-25M@mail.gmail.com>
	<4C910E9C.7040004@lerdorf.com>
Date: Wed, 15 Sep 2010 12:40:41 -0700
Message-ID: <AANLkTiknJ0hL0WNSSbg0_mCN+hAS-OoAhW9Wi4M_SDfv@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] nginx+php-fpm question
From: jravimenon@gmail.com (J Ravi Menon)

On Wed, Sep 15, 2010 at 11:21 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote=
:
> On 9/15/10 10:57 AM, J Ravi Menon wrote:
>> =A0So my guess is, if we do php-fpm approach, we have to do all these
>> cleanups manually? =A0Or are there simpler solutions or hook-ups that
>> does it automatically at the end of the request cycle?
>
> No, fastcgi doesn't change this model at all. =A0You have the same
> end-of-requests cleanups as with mod_php.
>
Ah good to know.


>> 2) My other concern is the extra ipc overhead between
>> nginx<---->php-fpm servers even on unix sockets. To me in theory
>> apache+mod_php ( + apc with stat off) should be as efficient as you
>> can get. Granted nginx might be more efficient in its socket mgmt
>> (non-blocking event-driven i/o), but can it really outperform the
>> apache approach given the issues in (1) are resolved?
>
> In theory that extra ipc should make the nginx case slower, true. =A0From
> what I have been able to measure, that is rarely a factor though.
>
> You can take a look at this slide from a recent talk of mine:
>
> =A0http://talks.php.net/show/drupalconcph/11
>
> That's testing a vanilla Drupal setup on Apache, PHP-FPM-nginx and
> PHP-FPM-lighttpd. =A0The dashed lines show the latency, the solid lines
> the requests/sec.

A lot here will depend upon the typical payload size. If compression
is done at the fcgi server end, I can see why it may not matter much.

Thx,
Ravi




>
> -Rasmus
>
>