Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49672
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.161.170 cause and error)
Message-ID: <4C910E9C.7040004@lerdorf.com>
Date: Wed, 15 Sep 2010 11:21:16 -0700
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: J Ravi Menon <jravimenon@gmail.com>
CC: internals@lists.php.net
References: <AANLkTinF=ZctV7e5jzGERJ_mZYn4R75fq1szsXJ4-25M@mail.gmail.com>
In-Reply-To: <AANLkTinF=ZctV7e5jzGERJ_mZYn4R75fq1szsXJ4-25M@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] nginx+php-fpm question
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 9/15/10 10:57 AM, J Ravi Menon wrote:
>  So my guess is, if we do php-fpm approach, we have to do all these
> cleanups manually?  Or 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.  You have the same
end-of-requests cleanups as with mod_php.

> 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.  From
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:

  http://talks.php.net/show/drupalconcph/11

That's testing a vanilla Drupal setup on Apache, PHP-FPM-nginx and
PHP-FPM-lighttpd.  The dashed lines show the latency, the solid lines
the requests/sec.

-Rasmus