Hmmm are you really sure that you want to move all of that to a remote server?
Really as I've been working more and more with LARGE ACTIVE sites (formerly zeldauniverse.net, and now mothering.com) I've found that apache is a very large part of issues. Apache is a _great_ webserver overall, however silly static things that get served several hundered times over and over again can make a signifncat load over time.
During E3 I was able to move (about 13 hours before it started) everything that was static (images, large media downloads, mp3's etc) to a remote server. The load drasticly droped down. On the remote server all I was using was lightttpd to serve all of the media.
I plan to follow this though on a new server setup I am working on for one of my clients. We are condensing our current network of main machines from 9 to 6 by way of a new setup.
Having a remote media server to deal with static images had been a big success.
Personally I'd rather avoid the default clustering matter as it just makes things much more complicated when it comes to serving attachments.
|