Re: phpng: Refactored PHP Engine with Big Performance Improvement

the performance difference may be significant. For example qdig. mod_php (PIC) 440 req/sec FastCGI (non-PIC) 537 req/sec The bechmark was done with 32-bit build of phpng. I didn't get time to investigate it in all details, but it'll really make sense. Thanks. Dmitry. On Thu, May 8, 2014 at 7:59 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote: > On 5/8/14, 5:48 AM, Zeev Suraski wrote: > > Again, this is just history/habits. > > Nothing prevents creation of apache-fastcgi-php5 package that'll do the > > exact same thing using FastCGI. > > What you are calling history/habits here is also knows as operational > stability. Every change to a stack incurs operational costs which has to > be balanced against the benefits of changing a component. Even though it > seems like a trivial thing to change from Apache/mod_php to > Apache/mod_fcgid or nginx+php-fpm, the operational cost can be quite > high. Consider changes to the Nagios monitoring setup. Dev VM images all > have to be updated. Startup/shutdown/deploy and logging systems might be > affected along with integration tests. And for most environments > changing doesn't actually buy you anything. A typical PHP request spends > so little time in the web server compared to waiting on mysql and > memcache replies that even a major performance boost doesn't actually > give you much. > > I fully agree that nginx+php-fpm is a nicer architecture. I like the > process separation that fastcgi brings and the saner and richer > configuration nginx brings along with the slight performance boost, but > even for my own use those benefits haven't outweighed the cost of > switching for me for systems that are running well under mod_php today. > > -Rasmus > >