Re: phpng: Refactored PHP Engine with Big Performance Improvement

From: Date: Thu, 08 May 2014 14:22:57 +0000
Subject: Re: phpng: Refactored PHP Engine with Big Performance Improvement
References: 1 2 3 4 5 6 7 8 9 10 11  Groups: php.internals 
Request: Send a blank email to internals+get-74058@lists.php.net to get a copy of this message
Btw, I'm of course advocating doing this as a part of PHP 7, and not in 5.6 or a minor version. There's going to be a migration process from 5.6 to 7, and I think this part would be one of the easiest to handle. Zeev > On 8 במאי 2014, at 17:02, Andi Gutmans <andi@zend.com> wrote: > > On May 8, 2014, at 5:46 AM, Zeev Suraski <zeev@zend.com> wrote: > >>> >>> For what it’s worth I don’t think we should stop supporting mod_php at this point >>> in time. >>> I think there are still plenty of situations where this is the easier, simpler route to >>> go and quite robust. >> >> Such as? >> >> FastCGI (or fpm) is just as robust, it's a lot more scalable and has mostly just >> advantages. The main thing mod_php has going for it is history. There are no real technological >> advances and the rise of PHP on nginx can attest to that. > > There are tools and know-how out there on configuring various aspects of PHP through > http.conf/.htaccess. Sure you can achieve most of that via FastCGI but I do not believe it’s as > simple and straightforward and I still believe the majority of the PHP community is using mod_php. > Re: nginx, the reality is, that while popular, it’s still not being used in the majority of > environments. It’s being used more on the big, scale-out properties than on the massive of smaller > PHP deployments. > > I guess we’ll need to agree to disagree on this one :) > > Andi >

« previous php.internals (#74058) next »