I got everything ready to make the move to WordPress 2.1… I backed up my database, I backed up all the php files. I deleted all the old files off the server and uploaded all the new ones. I read the warning about it needing MySQL 4.x, but I didn’t think anything of it. Surely Media Temple, a fairly high-end Web host, would be running the latest database.
Well, it turns out that they might be a bit too high-end.
Media Temple recently took another leap forward in their server configurations (they’re calling it Hosting 2.0) and ditched the traditional shared-server model for a state-of-the-art grid-server set up for people like me who don’t need a super-fly dedicated server. This helps avoid the bad-neighbor syndrome common in shared server models. In those situations, if you happened to be “sharing” server processes with someone who experiences severe traffic peaks on occasion, your Web site’s performance can suffer.
In the grid model, everyone is distributed across a big network of servers. Idle processes can be tapped from numerous sources to respond to traffic peaks. For the most part, everyone should be happy. Makes maintenance easier to, as a faulty box can be yanked from the grid without anyone’s Web site having to be switched over to a different server. This supposedly makes 100% uptime very do-able.
Bring this full circle, my aging account is unfortunately stuck on the shared-server until I upgrade to the grid. And it appears the shared-server environment isn’t getting MySQL 4.x. I think I’ll be upgrading to the grid sometime, but I have other things to think about right now.
WordPress 2.1 and its auto-saving and spell-checking (though I do have spell-check through a Firefox extension…), will have to wait.