<?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: DBJ &#8211; Advanced MySQL Replication &#8211; Improving Performance</title>
	<atom:link href="http://oracleopensource.com/2009/02/11/dbj-advanced-mysql-replication-improving-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://oracleopensource.com/2009/02/11/dbj-advanced-mysql-replication-improving-performance/</link>
	<description>two worlds inexorably colliding</description>
	<lastBuildDate>Tue, 05 Jan 2010 08:35:53 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sheeri Cabral</title>
		<link>http://oracleopensource.com/2009/02/11/dbj-advanced-mysql-replication-improving-performance/comment-page-1/#comment-1913</link>
		<dc:creator>Sheeri Cabral</dc:creator>
		<pubDate>Wed, 11 Feb 2009 22:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://oracleopensource.com/2009/02/11/dbj-advanced-mysql-replication-improving-performance/#comment-1913</guid>
		<description>The #1 cause of this type of slave lag that I have seen is poor query/schema design.  &quot;Optimize your schema, data and queries&quot; should be the very first thing to do.  GCN had a great article a while back on &quot;Secrets of Optimization&quot; written by Joab Jackson.  

http://gcn.com/Articles/2008/08/15/Secrets-of-optimization.aspx

The article goes into optimizing queries and schema.  However, there&#039;s a third aspect, optimizing your data.  This means having as small a data set as possible.  Can you move historical data to another table?  Can you use a SMALLINT instead of an INT?

Optimizing data/schema/queries solves 90% or more of common replication issues,  and unfortunately did not end up on the list.</description>
		<content:encoded><![CDATA[<p>The #1 cause of this type of slave lag that I have seen is poor query/schema design.  &#8220;Optimize your schema, data and queries&#8221; should be the very first thing to do.  GCN had a great article a while back on &#8220;Secrets of Optimization&#8221; written by Joab Jackson.  </p>
<p><a href="http://gcn.com/Articles/2008/08/15/Secrets-of-optimization.aspx" rel="nofollow">http://gcn.com/Articles/2008/08/15/Secrets-of-optimization.aspx</a></p>
<p>The article goes into optimizing queries and schema.  However, there&#8217;s a third aspect, optimizing your data.  This means having as small a data set as possible.  Can you move historical data to another table?  Can you use a SMALLINT instead of an INT?</p>
<p>Optimizing data/schema/queries solves 90% or more of common replication issues,  and unfortunately did not end up on the list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Newton</title>
		<link>http://oracleopensource.com/2009/02/11/dbj-advanced-mysql-replication-improving-performance/comment-page-1/#comment-1911</link>
		<dc:creator>William Newton</dc:creator>
		<pubDate>Wed, 11 Feb 2009 20:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://oracleopensource.com/2009/02/11/dbj-advanced-mysql-replication-improving-performance/#comment-1911</guid>
		<description>I don&#039;t think using MyIsam on the slave is such a good idea. Reads block writes with MyIsam. So if you have a slave for the long running read only queries .. MyIsam will cause replication to fall behind.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think using MyIsam on the slave is such a good idea. Reads block writes with MyIsam. So if you have a slave for the long running read only queries .. MyIsam will cause replication to fall behind.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
