<?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: Two Easy Ways to Expand Your MySQL Capabilities</title>
	<atom:link href="http://www.singlehop.com/blog/two-easy-ways-to-expand-your-mysql-capabilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.singlehop.com/blog/two-easy-ways-to-expand-your-mysql-capabilities/</link>
	<description>The Official SingleHop Blog</description>
	<lastBuildDate>Wed, 15 May 2013 18:14:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: jeffatrackaid</title>
		<link>http://www.singlehop.com/blog/two-easy-ways-to-expand-your-mysql-capabilities/comment-page-1/#comment-2963</link>
		<dc:creator>jeffatrackaid</dc:creator>
		<pubDate>Tue, 16 Feb 2010 21:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.singlehop.com/blog/?p=993#comment-2963</guid>
		<description><![CDATA[I typically start with a server analysis using syssat. This way you can pinpoint what needs upgrading.  MySQL is a RAM hungry beast, so try to give it as much as you can.  I&#039;ve seen entry level xeon servers with SATA disks and large amounts of RAM (16GB) handle loads very well.  

Also, never forget to tune your queries.  Using the slow query log and EXPLAIN can help you find and fix bad queries.  I&#039;ve seen overloaded servers go to near idle by simply fixing a few queries.  While this requires a lot of expertise, it can give you many-times the return as replication.  

Not all applications can easily be switched to send read-only statements to the slave, so before deploying replication, be sure your application can  effectively utilize your new slave server.]]></description>
		<content:encoded><![CDATA[<p>I typically start with a server analysis using syssat. This way you can pinpoint what needs upgrading.  MySQL is a RAM hungry beast, so try to give it as much as you can.  I&#8217;ve seen entry level xeon servers with SATA disks and large amounts of RAM (16GB) handle loads very well.  </p>
<p>Also, never forget to tune your queries.  Using the slow query log and EXPLAIN can help you find and fix bad queries.  I&#8217;ve seen overloaded servers go to near idle by simply fixing a few queries.  While this requires a lot of expertise, it can give you many-times the return as replication.  </p>
<p>Not all applications can easily be switched to send read-only statements to the slave, so before deploying replication, be sure your application can  effectively utilize your new slave server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
