On 05/02/16 20:14, Matus UHLAR - fantomas wrote: > and I mean, apache process loads all modules at startup time, which > means that mod-php is loaded only at the start or reconfigure time, > and all child processes are created by forking only when servers are > spawned at: > - startup > - increating number of server processes > - restarting after MaxRequestsPerChild or MaxConnectionsPerChild hit.
And my point is that every apache process includes the full mod-php interpreter regardless of whether that process is about to handle a PHP script or a static file. It's not the startup time that is the issue (for me) but that a PHP interpreter is included within each process even if it is not going to be used to interpret a PHP script (in the case of delivering a non-php static resource). ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
