On 3 December 2013 10:55, Chris Samuel <chris@csamuel.org> wrote:
On 03/12/13 10:46, Toby Corkindale wrote:
It's even in the PHP manual:
I suspect that's about using mod_php, not PHP per se, it says:
# If you want to use a threaded MPM, look at a FastCGI # configuration where PHP is running in its own memory space.
which is pretty much what I do (mod_fcgid) and it works well.
I'd agree with that. Using fastcgi is similar to using a reverse proxy. Rather than apache running the dynamic content generation, it's just dispatching queries to back-end app servers and then forwarding the results back to the client. (Which is different to trying to efficiently manage many php interpreters within a multi-threaded apache process) Given what we've heard about Tim's environment, I suspect the machines will have taken the simplistic option, and be running PHP within the Apache process, rather than as separate processes connected to Apache via a socket. T