6 ms·
Not sure where you take this "standard" from - AFAIR, it was mod_php since ~ 2004-2005 and all that lovely mpm_prefork stuff. FastCGI and FPM came a bit later.
by CoolCold 2y ago
Not sure where you take this "standard" from - AFAIR, it was mod_php since ~ 2004-2005 and all that lovely mpm_prefork stuff. FastCGI and FPM came a bit later.
> should be using proxy_fcgi with Apache
I'd in general use Nginx instead of Apache, until .htaccess handling is needed - which is still a thing in shared hosting and around area mostly from my perspective - if you really care about "squeeze out a bit of extra memory" of course.
- mhitza 2y agoI take it as a standard because its the approach recommended above all others in the Apache wiki [1] and probably what distros will do at some point as well (RedHat family distros already do this if you don't explicitly opt-in to use mod_php). [1] https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=115522403#content/view/115522403 https://cwiki.apache.org/confluence/plugins/servlet/mobile?c...
- CoolCold 2y agoThank you for clarification - makes a lot of sense what they state in that docs > Why you shouldn't use mod_php with the prefork mpm anymore > > mod_php is loaded into every httpd process all the time. Even when httpd is serving static/non php content, that memory is in use. > mod_php is not thread safe and forces you to stick with the prefork mpm (multi process, no threads), which is the slowest possible configuration I probably very biased here - I silently imply it's a Nginx in front of Apache in 99.9% cases - so serving static files and long-living connections is not a problem with mpm_prefork [for setups and system administration around me].