<?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: Top 84 MySQL Performance Tips</title>
	<atom:link href="http://www.debianadmin.com/top-84-mysql-performance-tips.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.debianadmin.com/top-84-mysql-performance-tips.html</link>
	<description>Debian/Ubuntu Linux System Administration Tutorials,Howtos,Tips</description>
	<lastBuildDate>Thu, 19 Nov 2009 13:24:32 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jet Profiler</title>
		<link>http://www.debianadmin.com/top-84-mysql-performance-tips.html/comment-page-1#comment-3742</link>
		<dc:creator>Jet Profiler</dc:creator>
		<pubDate>Thu, 01 Oct 2009 22:28:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.debianadmin.com/top-84-mysql-performance-tips.html#comment-3742</guid>
		<description>Thanks for a good list. Here are a few more tips:

-Use as short indexes as possible. Use smallint if you don&#039;t need a whole int. When indexing hex data (eg md5 hash), you can store it as two BIGINTs.
-Delete data that you don&#039;t need. Tables will grow, so monitor table sizes regularly. Use partitioning (or archive, or merge tables as mentioned above).
-Use SHOW PROFILES to get more details than EXPLAIN
-Monitor the heaviest queries, for example using Jet Profiler for MySQL</description>
		<content:encoded><![CDATA[<p>Thanks for a good list. Here are a few more tips:</p>
<p>-Use as short indexes as possible. Use smallint if you don&#8217;t need a whole int. When indexing hex data (eg md5 hash), you can store it as two BIGINTs.<br />
-Delete data that you don&#8217;t need. Tables will grow, so monitor table sizes regularly. Use partitioning (or archive, or merge tables as mentioned above).<br />
-Use SHOW PROFILES to get more details than EXPLAIN<br />
-Monitor the heaviest queries, for example using Jet Profiler for MySQL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Avani</title>
		<link>http://www.debianadmin.com/top-84-mysql-performance-tips.html/comment-page-1#comment-2304</link>
		<dc:creator>Avani</dc:creator>
		<pubDate>Wed, 28 Jan 2009 12:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.debianadmin.com/top-84-mysql-performance-tips.html#comment-2304</guid>
		<description>Its a totally helpfull material</description>
		<content:encoded><![CDATA[<p>Its a totally helpfull material</p>
]]></content:encoded>
	</item>
</channel>
</rss>
