<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Anatomy of MySQL on the GRID</title>
	<atom:link href="http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/</link>
	<description></description>
	<lastBuildDate>Wed, 18 Jan 2012 21:51:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Alex</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-476</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 05 Sep 2007 00:08:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-476</guid>
		<description>@DT,
Thanks for the kind words and brutal honesty. I see your problem is with moving a large DB. Were the KB articles we pointed to helpful or confusing? I&#039;ll email you as well.</description>
		<content:encoded><![CDATA[<p>@DT,<br />
Thanks for the kind words and brutal honesty. I see your problem is with moving a large DB. Were the KB articles we pointed to helpful or confusing? I&#8217;ll email you as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DT</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-475</link>
		<dc:creator>DT</dc:creator>
		<pubDate>Tue, 04 Sep 2007 23:41:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-475</guid>
		<description>I&#039;m no tech guy and really only understood less than 20% of the first sentence.  After that I just scrolled to the end interested in the conclusion.  But the point here is, strategically on a corporate level, you guys did the right thing.  Instead of keeping it in the labs, you launched it as best you knew how at that time.  You DID something, instead of endless test and wondering how to get it out.

After that you took the punches like a champ, rolled in the mud and continued to FIX it.  Launching a first mover product with very few competitors is always tough as you have no one to learn from.  In the end, this will be a success as you did something about it first and learnt along the way.  Even this blog is a good thing.

MT as a brand is very funny, the associations with the cool sites is one factor, but the badge is almost worn like a &quot;purple heart&quot; in a been there done that kinda of way.  That should mean something.

I just signed up, with lots of problems which i figured out, so where can i get my badge?</description>
		<content:encoded><![CDATA[<p>I&#8217;m no tech guy and really only understood less than 20% of the first sentence.  After that I just scrolled to the end interested in the conclusion.  But the point here is, strategically on a corporate level, you guys did the right thing.  Instead of keeping it in the labs, you launched it as best you knew how at that time.  You DID something, instead of endless test and wondering how to get it out.</p>
<p>After that you took the punches like a champ, rolled in the mud and continued to FIX it.  Launching a first mover product with very few competitors is always tough as you have no one to learn from.  In the end, this will be a success as you did something about it first and learnt along the way.  Even this blog is a good thing.</p>
<p>MT as a brand is very funny, the associations with the cool sites is one factor, but the badge is almost worn like a &#8220;purple heart&#8221; in a been there done that kinda of way.  That should mean something.</p>
<p>I just signed up, with lots of problems which i figured out, so where can i get my badge?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mohamed</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-471</link>
		<dc:creator>Mohamed</dc:creator>
		<pubDate>Wed, 15 Aug 2007 13:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-471</guid>
		<description>And now the non-technical summary: a nicely put together architecture for handling the assorted nasty things that end users do to hosting sites and likely to get significantly more robust and capable once the improvements are in place. Lots of good work went on there.</description>
		<content:encoded><![CDATA[<p>And now the non-technical summary: a nicely put together architecture for handling the assorted nasty things that end users do to hosting sites and likely to get significantly more robust and capable once the improvements are in place. Lots of good work went on there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The &#8220;Break it Down&#8221; Blog &#187; Blog Archive &#187; Media Temple - Problem #2</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-460</link>
		<dc:creator>The &#8220;Break it Down&#8221; Blog &#187; Blog Archive &#187; Media Temple - Problem #2</dc:creator>
		<pubDate>Fri, 04 May 2007 23:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-460</guid>
		<description>[...] Ok the site was just down again for a few hours with exactly the same problem I reported before&#8230; In a fit of rage a friend of mine pointed me to this blog post from the (mt) team explaining why the MySQL outtages occur so often (abusive users). It sounds like when you become abusive with your usage, you are automatically moved onto a quarentined MySQL Container instance&#8230; that&#8217;s pretty slick&#8230; I hope they move all the crap-bags off my shared server so I stop going off line. [...]</description>
		<content:encoded><![CDATA[<p>[...] Ok the site was just down again for a few hours with exactly the same problem I reported before&#8230; In a fit of rage a friend of mine pointed me to this blog post from the (mt) team explaining why the MySQL outtages occur so often (abusive users). It sounds like when you become abusive with your usage, you are automatically moved onto a quarentined MySQL Container instance&#8230; that&#8217;s pretty slick&#8230; I hope they move all the crap-bags off my shared server so I stop going off line. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-453</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Mon, 26 Feb 2007 07:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-453</guid>
		<description>I&#039;ve never personally had any problems using mysql on the grid, but it&#039;s good to see such honesty and dedication coming from a hosting company. I was &quot;kicked off&quot; my old host, it wasn&#039;t for inefficient software (I just use wordpress), but from a few traffic spikes, and MT was exactly what I was looking for. Keep up the good work!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve never personally had any problems using mysql on the grid, but it&#8217;s good to see such honesty and dedication coming from a hosting company. I was &#8220;kicked off&#8221; my old host, it wasn&#8217;t for inefficient software (I just use wordpress), but from a few traffic spikes, and MT was exactly what I was looking for. Keep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald Heft</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-450</link>
		<dc:creator>Ronald Heft</dc:creator>
		<pubDate>Fri, 23 Feb 2007 04:04:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-450</guid>
		<description>You&#039;re 1.2 Grid announcement mentions to visit this post to become a part of the beta. I&#039;m interested in the beta, where can I sign up?</description>
		<content:encoded><![CDATA[<p>You&#8217;re 1.2 Grid announcement mentions to visit this post to become a part of the beta. I&#8217;m interested in the beta, where can I sign up?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Digg Meets Grid-Server - JakeJarvis.com</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-432</link>
		<dc:creator>Digg Meets Grid-Server - JakeJarvis.com</dc:creator>
		<pubDate>Sun, 28 Jan 2007 23:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-432</guid>
		<description>[...] That&#8217;s not to say the Grid is flawless, however. I&#8217;ve seen an insane amount of downtime during periods of very little activity, which is partially why I moved my projects over to DreamHost. Despite the flaws, I&#8217;ve decided to stick it out for at least a few more months to see how they pull through with the fix to their biggest problem &#8212; MySQL. (Plus, I racked up a few complementary months between referrals and complaining to the helpdesk about the downtime.)             No Comments   Leave a CommentThere was an error with your comment, please try again. name (required)email (will not be published) (required)url [...]</description>
		<content:encoded><![CDATA[<p>[...] That&#8217;s not to say the Grid is flawless, however. I&#8217;ve seen an insane amount of downtime during periods of very little activity, which is partially why I moved my projects over to DreamHost. Despite the flaws, I&#8217;ve decided to stick it out for at least a few more months to see how they pull through with the fix to their biggest problem &#8212; MySQL. (Plus, I racked up a few complementary months between referrals and complaining to the helpdesk about the downtime.)             No Comments   Leave a CommentThere was an error with your comment, please try again. name (required)email (will not be published) (required)url [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Day</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-431</link>
		<dc:creator>James Day</dc:creator>
		<pubDate>Sat, 27 Jan 2007 08:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-431</guid>
		<description>And now the non-technical summary: a nicely put together architecture for handling the assorted nasty things that end users do to hosting sites and likely to get significantly more robust and capable once the improvements are in place. Lots of good work went on there.</description>
		<content:encoded><![CDATA[<p>And now the non-technical summary: a nicely put together architecture for handling the assorted nasty things that end users do to hosting sites and likely to get significantly more robust and capable once the improvements are in place. Lots of good work went on there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-426</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Thu, 25 Jan 2007 18:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-426</guid>
		<description>I&#039;d love to be able to look at efficiency on my end of the databases, but I cannot (and frankly, will not) look to revise my db until such problems on the server side are worked out.  In the two weeks I have been with mt, my site has been reliably quick at times, sometimes extremely slow, and other times it has been completely down.  While transparency is a good thing, such issues were not posed to me when I entered into a contract with mt.  So, after the fact, I&#039;m left with a site that I cannot present to the public, and I have no idea of the reliability that future changes will bring to my site&#039;s speed.  Once again, I&#039;m impressed by the grid build, but very unimpressed at the fact that you are serving a product that is incomplete.  Granted I could wait a few months, and see what occurs (and I&#039;d like to), but can we assume the best on March 1?</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to be able to look at efficiency on my end of the databases, but I cannot (and frankly, will not) look to revise my db until such problems on the server side are worked out.  In the two weeks I have been with mt, my site has been reliably quick at times, sometimes extremely slow, and other times it has been completely down.  While transparency is a good thing, such issues were not posed to me when I entered into a contract with mt.  So, after the fact, I&#8217;m left with a site that I cannot present to the public, and I have no idea of the reliability that future changes will bring to my site&#8217;s speed.  Once again, I&#8217;m impressed by the grid build, but very unimpressed at the fact that you are serving a product that is incomplete.  Granted I could wait a few months, and see what occurs (and I&#8217;d like to), but can we assume the best on March 1?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos</title>
		<link>http://weblog.mediatemple.net/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-425</link>
		<dc:creator>Carlos</dc:creator>
		<pubDate>Thu, 25 Jan 2007 15:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.mediatemple.net/weblog/2007/01/19/anatomy-of-mysql-on-the-grid/#comment-425</guid>
		<description>Poor scalability with Mysql? Hardly a surprise for anyone who does more performance testing than &quot;select count(*) from foo&quot; in a single thread. In a read-only environment, sure, Mysql may be sufficient, but for highly concurrent OLTP load - forget it. Btw, I found the following articles that pretty much sums it up:

http://pda.tweakers.net/?reviews/661
http://pda.tweakers.net/?reviews/657
http://pda.tweakers.net/?reviews/649</description>
		<content:encoded><![CDATA[<p>Poor scalability with Mysql? Hardly a surprise for anyone who does more performance testing than &#8220;select count(*) from foo&#8221; in a single thread. In a read-only environment, sure, Mysql may be sufficient, but for highly concurrent OLTP load &#8211; forget it. Btw, I found the following articles that pretty much sums it up:</p>
<p><a href="http://pda.tweakers.net/?reviews/661" rel="nofollow">http://pda.tweakers.net/?reviews/661</a><br />
<a href="http://pda.tweakers.net/?reviews/657" rel="nofollow">http://pda.tweakers.net/?reviews/657</a><br />
<a href="http://pda.tweakers.net/?reviews/649" rel="nofollow">http://pda.tweakers.net/?reviews/649</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

