BlogCadre users see no ads!  Popular topics: humor, video, links, cool, wtf.  Go create an account!




Upgrading to Media Temple's Grid Servers

Media Temple Grid ServerBlogCadre just made the upgrade from Media Temple's shared server platform to their new "Grid Server" system.

New GS Features
Instead of a shared server, the GS system places all your data on an NFS server. There are apparantly several load-balanced front end web servers that then access this data from the common data location. Ben over at cuddletech has some more details on the Grid Server set up.

Read on for more info about the transition, including migration notes and my skepticism as to whether or not this service is even a good move. If you want the 5 second version: the transition is frightening with no staging process or backout plan, and the "upgrade" leaves us with half the bandwidth and the real potential for expensive new mystery charges.

On the plus side, this upgrade should mean improved server response times, more mysql connections, and scalability under heavy loads, but I'm not sure how the external mysql server and data storage will affect read/write performance on a database heavy site.

One thing that's nasty, though, is that you are now billed for Grid Processor Units in addition to bandwidth and disk space. GPUs are supposedly based on processor use and disk access, but there is no mention of what that actually means. Supposedly, the allotted amount is way more than almost anyone will use, but it still freaks me out.

How many GPUs does BlogCadre use in a typical day? No idea. What happens if some glitch causes a script to go haywire? Instead of slowing my server down is it going to ring up a thousand dollar fee? With all these load balanced servers handling my site, will I even know if one server is chugging down and eating CPU, costing me money? As of this posting, even after the upgrade there is no way to even see how many GPUs you are using. That scares the hell out of me.

Finally, to keep the same monthly rate, I had to go with "Grid Server Lite" instead of paying two and a half times as much for the full package. This means half the GPUs (500--whatever the heck that means), and half the bandwidth (500GB). So that's half the bandwidth I used to have and the potential for new costs for the same base price. Yippee!

Freakiest Site Move Ever
In all, I'm not too happy with the process. While the transition is completely automated, there is no staging phase. They pack up your files, shut down the old setup, drop your stuff on the new server and switch the DNS record. There is no opportunity to configure the new site before the old one is shut down, and there is no way to back out of the transition if something goes wrong. It's like playing russian roulette with six bullets.

If anyone else out there is making the upgrade, here are the "gotchas" I ran into:

MySQL: The server will change from localhost to something else. The address of the new mysql server will be a mystery until the files are moved and your busted new site is launched. You'll need to ssh in quickly and update your config/scripts.

SSH: Confounding your scramble to update your settings, your server IP and username have also changed. Unfortunately, I found no mention of the new ssh info in the migration documentation, though I was able to dig some information up in the knowledge base. If your old access was domainname@domainname.com, your new account is serveradmin%domainname@domainname.com

Compatability: After updating the MySQL settings, things seem to be working correctly across the board. I have no reason to believe this isn't normal, but I'm feeling awfully lucky since there was no back-out procedure.

Lost Files: My html directory made it, but I had a lot of install files, backups and new upgrade versions that I was working on in my home directory. That appears to be gone after the move. There is a directory on the new server that I think may be housing all of these files, but its permissions are set wrong and I cannot access it.

Support: I've been with MT for a couple years and I've encouraged a lot of people to switch to MT for one reason: incredible support service. Not so with this transition. It used to be that you could submit a support request and a qualified server admin would email you back literally within minutes. I submitted support requests for a couple of transition issues (namely my lost files) and haven't even received a "looking into it" response. It's been an hour or two now. What's going on Media Temple??

Anyway, time will tell how this new system performs. I really hope it's awesome as hell, because MT has been such a great hosting provider in the past. At the moment, I've got some concerns, though. With new potential charges, less bandwidth, and no static IP, this forced upgrade feels like it might be a downgrade in disguise.

Trackback URL for this post:

http://www.blogcadre.com/trackback/2117

Hope it turns out well in the long run

a person's picture

I'd hate to see BC in trouble, so I hope the transition is a good one.

So any issues yet??

Just curious, how are things in the new cluster?

-Ryan Larson
Junster.com

Sort of...

Jason Striegel's picture

I'm not impressed so far. I think they've oversold way past their server capacity... I know overselling is part of how you make things affordable, but I think typical load is saturating things, not extraordinary traffic.

I haven't had any bandwidth issues, but it would be practically impossible to hit those bandwidth numbers with the page load time. Static pages seem to load fast, but the blog performance is abysmal. I believe the mysql connection is the bottleneck, if I had to make any bets. I haven't done any extensive testing with non-mysql dynamic code, but the stuff I'm experiencing is pretty indicative of slow mysql connection response time.

I'm just hoping that they manage to work the kinks out. I like the idea of having cheap hosting on a load-balanced platform, and I bet it makes sense from their administration and cost perspective as well. They should be able to utilize servers better this way.

The other thing that still worries me is that their GPU definition still hasn't been defined. Only a vague definition of "some unit of processing and disk use," which is completely nebulous. I think they are waiting to see what normal load is before they define their GPU yardstick, so essentially they can tax their top x% of users and force them into a more expensive setup. I just hope x is a small number...

Seems your not the only one with issues..

Looks like some other people have been having issues with the mysql connectivity. Hope version 1.1 helps.

http://news.netcraft.com/archives/2006/11/29/outages_for_mediatemple_grid_hosting_service.html

-Ryan Larson
Junster.com