Current set up;
I have a single dedicated server running a web site (it's a lamp stack forum)
- OS : CentOS
- CPU : Dual 3.2Ghz Quad-core Xeons
- RAM : 40GBs (10x4GB DIMMs)
- Storage : Software RAID1 with 2x 7.2k SATAII 500GB HDD
- The forum MySQL DB is around 10GBs
- The web root is around 1.5GBs (mostly user uploaded pictures)
I want to tune the server as much as I can to use the hard disks as little as possible. I feel they are the Achilles heal here. No funds are available for any hardware changes so I have been exploring software performance enhancing options.
I have done some reading about Varnish and memcached. The PHP forum has support for memcached (The vendors provide instructions for enabling it in the configuration files) so I should be able to install and use that. I figure I can bind Apache2 to the loopback/127.0.0.1 interface instead of its public facing interface and install varnish binding it to the public facing interface passing requests back to Apache on 127.0.0.1.
I will likely start separate questions about Varnish and memcached later about their technical configuration, for now I am after input on this as a design idea. This all sounds like reasonable logic to me, but is it in fact a bonkers approach? Many people use both of these caching packages with great success, is it likely they will lift demand on the hard disks in this situation? If not, what else should I be looking at?