Nick Hill wrote:
I understood the server was I/O bound from a recent posting. Server maxed out with low CPU utilisation. The information you and I have differs. You are in a position to have better information on this than I. I certainly don't want to waste time solving a non-existent problem.
Yes, well, you weren't completely misinformed, but just missed one crucial detail. :-) We are currently I/O bound on the db server because the one that we're using sucks. It's what we are limping by on until the new hardware is installed, or until I manage to find something for Brion to put into service.
Do we have a bottleneck? If so, where is it and how do we know?
Bigger picture, I think that the configuration that we've discussed is the right way to go, and no exotic hardware configurations are needed to serve the website quickly, effectively, and reliably.
squids->webservers->db servers
with auxiliary servers for other jobs.
I'm putting the finishing touches on an order at Silicon Mechanics right now, and I'll report back to everyone once I have all the details and a firm delivery date promise.
--Jimbo