3yardsandacloud said:
Thanks for the info. Dryden. What (as far as you know) is the possibility of the old server becoming a redundant system in case of a catastrophic failure. I know this would be severly underpowered, but would it (I'm guessing) be able to limp us through in the short term?
Well, the current server we're using, as I've come to understand it from Clarity, will still be left in AZ and be available. So, since all this software will still be there, if there were an emergency we could quickly switch off the new server back to the old one (old one meaning the one we're using right now). It wouldn't be difficult to mirror the most important things, leaving this server as a complete hot spare. The issue, of course, is processing speed (the whole reason for the new server), so we'd have to address that down the road once there is a ballpark figure for what server load will look like come October/November this year.
The easiest way to speed up the usability of the site on this current underpowered machine would be to cripple some of the non-essential features of vBulletin which prompt a database lookup. Disabling searches outright ... not allowing guests at all ... turning off sigs, avatars ...
For example, disabling avatars, sigs, and rep sitewide would eliminate 3 lookups per post @ 15 posts per page (default) = 45 non-essential lookups eliminated per page view.
EDIT: Forgot about vCash, medals/awards, and member titles .. that's another 45 non-essential lookups eliminated per page view. Do both and you wipe out 90 per view. This alone would cut server load nearly in half. Yeah ... they're nifty features, but we have to draw the line when we're on emergency standby.