Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
highload-php-en
Home
+ new post
About this group
Join this group
Message from discussion FPM in 5.3
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Peter Mescalchin  
View profile  
 More options Jul 23 2010, 8:40 pm
From: Peter Mescalchin <peter.mescalc...@gmail.com>
Date: Fri, 23 Jul 2010 17:40:05 -0700 (PDT)
Local: Fri, Jul 23 2010 8:40 pm
Subject: Re: FPM in 5.3
Print | View thread | Show original | Report this message | Find messages by this author
It appears you need to enable the new FPM SAPI (--enable-fpm) - so I
would assume the old one still remains for those that need it?

http://www.php.net/manual/en/install.fpm.install.php

Tom, I have used your very handy article for PHP setups in the past
for Apache2+PHP-FCGI - I'm sure if apache2 can run using the new php-
fpm it will makes things all that little more sweeter.

On Jul 24, 8:21 am, Tom Boutell <t...@punkave.com> wrote:

> I just saw the announcement of the FPM being included in PHP 5.3.3.
> That's great news - it sounds like the new FPM is a very good one. But
> I'd appreciate some clarification on the status of the old FPM in php-
> cgi.

> As described here:

> http://www.fastcgi.com/drupal/node/5?q=node/10

> The regular php-cgi binaries in 5.2.x and, in my experience, 5.3.0
> through 5.3.2 already include the capability of running as a FastCGI
> process manager (that is, managing multiple processes themselves). And
> this provides the essential feature of a shared APC cache.

> Also it sounds like the new SAPI has a separate binary, unlike the old
> FPM support which looked for environment variables and altered the
> behavior of php-cgi.

> So my questions are:

> 1. Was the old FPM removed from php-cgi in 5.3.3?

> 2. If so, wouldn't this cause considerable disruption for those of us
> who are using it if we upgrade to 5.3.3? If so, documentation of what
> to do in order to transition between the FPMs would be very useful.

> 3. Does the new FPM provide shared APC cache as the old one did? That
> feature is a lifesaver for object oriented code on a modest virtual
> machine.

> I have a widely forwarded article here which I'll update with the
> answers once I have them:

> http://window.punkave.com/2010/03/08/faster-php-kill-kill/

> Thanks!

> On May 26, 11:29 am, Antony Dovgal <t...@daylessday.org> wrote:

> > Hello all.

> > After a short discussion with Rasmus and Johannes (how's maintaining PHP 5.3 branch) it was agreed that FPM
> > can't break anything serious and even though 5.3 is a bugfix branch, it's safe to add FPM there.

> > Which was done several minutes ago.

> > So now you don't have to checkout PHP trunk, copy sapi/fpm to your 5.3 source tree and so on - it's all there already.
> > Snapshots containing FPM will be ready in ~1 hour, according tohttp://snaps.php.net.
> > Feel free to test them and report any issues you find using the official bug tracker @http://bugs.php.net.

> > P.S. no way to add it to 5.2, sorry.

> > --
> > Wbr,
> > Antony Dovgal
> > ---http://pinba.org-realtime statistics for PHP


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google