<?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: Video:  How to Stop Hating MySQL</title>
	<atom:link href="http://www.pythian.com/news/1354/how-to-stop-hating-mysql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/1354/how-to-stop-hating-mysql/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:01:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: OpenSQL Camp is in full swing!</title>
		<link>http://www.pythian.com/news/1354/how-to-stop-hating-mysql/#comment-300055</link>
		<dc:creator>OpenSQL Camp is in full swing!</dc:creator>
		<pubDate>Sat, 15 Nov 2008 16:35:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/1354/how-to-stop-hating-mysql#comment-300055</guid>
		<description>[...] Video: How to Stop Hating MySQL [...]</description>
		<content:encoded><![CDATA[<p>[...] Video: How to Stop Hating MySQL [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sheeri Cabral</title>
		<link>http://www.pythian.com/news/1354/how-to-stop-hating-mysql/#comment-300045</link>
		<dc:creator>Sheeri Cabral</dc:creator>
		<pubDate>Sat, 15 Nov 2008 16:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/1354/how-to-stop-hating-mysql#comment-300045</guid>
		<description>Tom -- I&#039;ve added the video, so you (and everyone else) can get the full information.  The short version is that using innodb_file_per_table can help optimize disk usage because each InnoDB table has a file for indexes and data.

As far as opening tables, you can increase the size of table_cache.</description>
		<content:encoded><![CDATA[<p>Tom &#8212; I&#8217;ve added the video, so you (and everyone else) can get the full information.  The short version is that using innodb_file_per_table can help optimize disk usage because each InnoDB table has a file for indexes and data.</p>
<p>As far as opening tables, you can increase the size of table_cache.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Krouper</title>
		<link>http://www.pythian.com/news/1354/how-to-stop-hating-mysql/#comment-299203</link>
		<dc:creator>Tom Krouper</dc:creator>
		<pubDate>Thu, 13 Nov 2008 03:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/1354/how-to-stop-hating-mysql#comment-299203</guid>
		<description>I was going through your slides and they were obvious just an outline for your talk. But, I did have one quick question... you mentioned innodb_file_per_table but it was just a line item. I couldn&#039;t tell if you were pro or anti (or neither). I&#039;ve heard different takes on using this. I know it is nice for saving space if you are doing lots of deletes followed by optimizing, but I&#039;ve also heard that once you get above 200 tables, there is a hit on performance with opening tables. I was hoping you could give your opinion on when to use or not use innodb_file_per_table. Thanks.</description>
		<content:encoded><![CDATA[<p>I was going through your slides and they were obvious just an outline for your talk. But, I did have one quick question&#8230; you mentioned innodb_file_per_table but it was just a line item. I couldn&#8217;t tell if you were pro or anti (or neither). I&#8217;ve heard different takes on using this. I know it is nice for saving space if you are doing lots of deletes followed by optimizing, but I&#8217;ve also heard that once you get above 200 tables, there is a hit on performance with opening tables. I was hoping you could give your opinion on when to use or not use innodb_file_per_table. Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

