News for hackers. Stuff that matters.
Re:Ask HN: Re-architecting on Slicehost to handle 50+ apache... by mandric on Thursday April 02, 2009 @02:18PM (#543789)
"you'll literally _have_to_ to different media serving and load balancing if you plan to grow whatever_this_is."

I guess my point is that it's a mod_php issue and I may not need nginx. My plan is to try a threaded apache without mod_php and use mod_fcgi for php. If that doesn't work then try a threaded apache with mod_php and see what happens.

Another solution is find another provider that offers more memory and similar service for the same price. But it will be hard to match slicehost's service I think.

Re:Ask HN: Re-architecting on Slicehost to handle 50+ apache... by markh on Thursday April 02, 2009 @02:37PM (#543823)
fastcgi with Apache will be a waste of your time I think.

Apache+php is solid, but a memory hog. If you want to keep things simple, move to Nginx with php+fastcgi. This is the suggested config for Slicehost.

Or, as previously suggested, offload the client connection to an Nginx server sitting in front of Apache. This will relieve the pressure on the php instances and will also handle static file serving.