On Oct 27, 2015 05:38, "Arkadiusz Miśkiewicz" <ar...@maven.pl> wrote: > > On Monday 26 of October 2015, Yehezkel Horowitz wrote: > > First, thanks Nick for the feedback. > > > > I have submitted https://bz.apache.org/bugzilla/show_bug.cgi?id=58550 as > > you suggested. > > > > >If a threaded MPM really isn't an option (for most users the obvious > > >solution), then the question is what works for you. > > > > I can't use threaded MPM as PHP (at least my version) doesn't support it. > > Not only yours. php doesn't support thread safety for normal usage... it's > marked experimental for ages: > > From php 5.6/7.0 configure help: > > " --enable-maintainer-zts Enable thread safety - for code maintainers only!!"
In general, the thread safety does work, but is not as efficient as it could be. Which is why most php developers and users rely on fastcgi (in httpd, either through mod_fcgid or mod_proxy_fcgi). It is generally cleaner and more efficient to run a smaller pool of php fcgi responders to service most applications, keep the benefits of the event (or worker) mpm in httpd. mod_php is a bit heavyweight to hold memory reservations on every httpd worker. Properly tuned you should see excellent performance, depending on whether your php scripts tend to block (remote SQL access, for example) - but efficient php can probably be tuned at 2 workers per core and adjust from there.
