Support » Everything else WordPress » Stay Away from Media Temple's Grid Service (gs)

  • At this point in time Media Temple has had years to correct major problems across their grid service (gs), most of all the excruciatingly slow query response time that brings applications like WordPress to a crawl, if not down.

    Tests using the Latency plugin and other resources have been written about by the plugin’s developer, and I have written about it as well.

    Despite some brief improvements after adding dedicated SQL resources (+$20/mo.) and being moved to a new cluster this spring, my experience on the grid returned this fall to the slowness and downtime I have usually experienced since opening it in 2008. Two other accounts without containers on different clusters have always been extremely slow with high levels of downtime. If you do a little research on the web, you will find these are not isolated issues.

Viewing 3 replies - 1 through 3 (of 3 total)
  • DigitalSquid


    Interesting post!

    I use Media Temple’s GS for quite a few WordPress sites for a couple of years. In my experience, I haven’t had any major downtime or noticed a massive speed difference between those sites and my non-Media Temple hosted ones. However, I would definitely agree that the Media Temple sites are slightly slower and lag more often.

    I’ve installed the Latency plugin on a few of the high traffic sites. If it does show that there is a significant level of latency I will definitely be changing web hosts.

    Thanks for the info.

    If you log uptime with a 24×7 type of service, I will be surprised if you see 99% for a month.

    Response time is critical if WP (or any other db-driven app) is a key work environment for 1+ users, if you want visitors to interact with each other (or you), if it’s an ecommerce site, etc.

    If you have lightweight pages, if you don’t use a lot of plugins, if you use caching well, and if you are not doing much more than publishing posts now and then, the grid is workable–albeit more costly than faster and cheaper hosts.

    If you have much going on in WP, an SQL container on the grid will make it a lot faster (and double the cost) but still not fast to the point that you consistently perceive an instantaneous response in the range of half a second. If you compare with a really fast account, you will start to notice the difference.

    Try the latency plugin on vanilla installs on different hosts. I did that along with http response logging with 2 shared hosts, 3 different (gs) accounts, and a moderately trafficked WP site in production on a (dv) earlier this year. The grid’s sql latency stuck out very clearly. You can see this just by hitting WP out of the box with 500-1000 page requests from a load testing script or

    The sluggishness of the grid stands out strongly in a way you can feel when you are spending hours working in the UI. Especially with heavier applications like a customized Joomla or Drupal site, on the grid any backend page load usually takes at least 1s+. I’m working with a new install of Joomla+Virtuemart on BlueHost right now, and it’s at the optimal response speed of <1s and often ~.5s. It feels pretty instantaneous, which is usually in the .1s range. After 1s people perceive a delay and their mind wanders.

    Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    We generally don’t leave posts like this (host recommendations and dis-recommendations as it goes) open. Sorry you’re having such a rough time on it, but this isn’t the tableau to bash a host.

    Updated to add… As the page for recommended hosting says this:

    […] if you have a favorite host you think we should feature here, email hosting dash application at this domain.

    I would suggest you use that email to send them a note why a host should be removed.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Stay Away from Media Temple's Grid Service (gs)’ is closed to new replies.