On 29 November 2013 17:08, Tim Connors <tconnors@rather.puzzling.org> wrote:
On Wed, 27 Nov 2013, Toby Corkindale wrote: [snip]
Secondly, if you're really stuck with Apache, and can't put decent reverse proxy accelerators in front of them, then try switching over the event-based worker? http://httpd.apache.org/docs/current/mod/event.html
That would be good, but rhel5&6 are still on apache 2.2, and event is marked as experimental there :( http://httpd.apache.org/docs/2.2/mod/event.html
We'll be stuck on rhel5 in production for years to come up at the current rate.
Ugh :(
I wonder about worker vs prefork? linux processes are lightweight, so I don't imagine threading is going to be much better. We only fork one process per second typically, and I don't think there'll be many differences in context switch overhead between the two. Worker apparently "sucks for php", but I don't know whether that's for mod_php or cgi or whatever.
That's OK though, because you're following the highly recommended practice of not using the same Apache instance for dynamic (ie. php) content as for static content, right? So you can switch the static handling over to mpm worker, and leave PHP on the prefork setup. T