You may also want to investigate Apache in worker mode with php-fpm running via fCGI. I switched a VM to that combo recently and the memory consumption by Apache dropped significantly. Also, you can then disable lots of apache modules to make it even leaner. Also, consider new relic monitoring of your servers. That allowed us to spot all sorts of PHP and MySQL related bottlenecks. Sent from my mobile device.
On 30 Nov 2013, at 8:53 am, Chris Samuel <chris@csamuel.org> wrote:
On Fri, 29 Nov 2013 05:08:58 PM Tim Connors wrote:
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.
Well I switched from prefork to worker on my personal Debian VM so that it could cope with lots of PHP, I kept running out of RAM otherwise.
Worked really well and my problems went away.
Now of course it's not loaded anything like the BoM servers, but this is the first I've heard that it "sucks for php".
cheers, Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main