Comments on: MediaTemple Performance http://nslog.com/2007/02/23/mediatemple_performance The Weblog of Erik J. Barzeski Sat, 30 Aug 2008 12:53:50 +0000 http://wordpress.org/?v=2.6.1 By: Steve T. http://nslog.com/2007/02/23/mediatemple_performance#comment-41005 Steve T. Wed, 04 Apr 2007 01:12:54 +0000 http://nslog.com/2007/02/23/mediatemple_performance#comment-41005 I feel your pain. At first, everything was good with the (dv)2.0. This, of course, came after a jumped off the (gs) ship. Then came (dv)3.0 which made me even happier. I've noticed though, over the past month, the server access has been lagging. FTP access was always uncomfortably slow, but just today I started paying attention to server ping times. They average about 97ms and the packet loss is 25%! I am not making this up. Now, I am located in Annapolis, MD, but does that mean I have to settle for crappy hosting quality because I am 3000 miles away? Anyway, I just sent out a support request, but it feels more like a bug report. The problem is not with my (dv)3.0 server, it's with MEDIATEMPLE. Type the following into a windows command prompt and see what you get: "ping -n 20 mediatemple.net". I also did a tracert on mediatemple and found that the Los Angeles hops are SERIOUSLY LAGGING which means, in theory, that anyone outside California would see poor server response when trying to access ANYTHING hosted on MediaTemple's servers. Bah! On a side note, I looked into hosting on my own Verizon Fios at home, but I found out that Verizon crippled this possibility for residential users by blocking inbound connections to port 80 and 443(I think). Great. So I have to pay a minimum of $99/month to get a dedicated IP and 15Mbps down / 2 Mbps up. To be honest, though, this would actually be a SIGNIFICANTLY faster connection than what I get with MediaTemple right now. Plus, I would already be AT the server. Why don't they just come out and say, "If you want reliable hosting, you're going to have to pay $A,NAR,MAN,DAL.EG!" GRRR! I feel your pain. At first, everything was good with the (dv)2.0. This, of course, came after a jumped off the (gs) ship. Then came (dv)3.0 which made me even happier. I've noticed though, over the past month, the server access has been lagging. FTP access was always uncomfortably slow, but just today I started paying attention to server ping times. They average about 97ms and the packet loss is 25%! I am not making this up. Now, I am located in Annapolis, MD, but does that mean I have to settle for crappy hosting quality because I am 3000 miles away? Anyway, I just sent out a support request, but it feels more like a bug report. The problem is not with my (dv)3.0 server, it's with MEDIATEMPLE. Type the following into a windows command prompt and see what you get: "ping -n 20 mediatemple.net". I also did a tracert on mediatemple and found that the Los Angeles hops are SERIOUSLY LAGGING which means, in theory, that anyone outside California would see poor server response when trying to access ANYTHING hosted on MediaTemple's servers.

Bah! On a side note, I looked into hosting on my own Verizon Fios at home, but I found out that Verizon crippled this possibility for residential users by blocking inbound connections to port 80 and 443(I think). Great. So I have to pay a minimum of $99/month to get a dedicated IP and 15Mbps down / 2 Mbps up. To be honest, though, this would actually be a SIGNIFICANTLY faster connection than what I get with MediaTemple right now. Plus, I would already be AT the server.

Why don't they just come out and say, "If you want reliable hosting, you're going to have to pay $A,NAR,MAN,DAL.EG!"

GRRR!

]]>