<?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: A quick rundown of per-thread buffers</title>
	<atom:link href="http://themattreid.com/wordpress/2009/04/28/a-quick-rundown-of-per-thread-buffers/feed/" rel="self" type="application/rss+xml" />
	<link>http://themattreid.com/wordpress/2009/04/28/a-quick-rundown-of-per-thread-buffers/</link>
	<description>MySQL DBA &#124; Linux&#039;er</description>
	<lastBuildDate>Thu, 26 Apr 2012 16:12:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: chrisz</title>
		<link>http://themattreid.com/wordpress/2009/04/28/a-quick-rundown-of-per-thread-buffers/comment-page-1/#comment-93</link>
		<dc:creator>chrisz</dc:creator>
		<pubDate>Thu, 09 Jul 2009 17:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://themattreid.com/wordpress/?p=157#comment-93</guid>
		<description>If you need to commit that much memory to a buffer, do it in the query :)   That&#039;s funny a funny cnf.</description>
		<content:encoded><![CDATA[<p>If you need to commit that much memory to a buffer, do it in the query <img src='http://themattreid.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />    That&#8217;s funny a funny cnf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://themattreid.com/wordpress/2009/04/28/a-quick-rundown-of-per-thread-buffers/comment-page-1/#comment-81</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 30 Apr 2009 14:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://themattreid.com/wordpress/?p=157#comment-81</guid>
		<description>Yes, you *can* overcommit memory and have things be fine up until that memory is actually addressed and the machine starts to swap to disk. That&#039;s when things get dirty. If you need to allocate that much ram to your buffers you&#039;re better off installing 64GB of ram. Overcommitting memory is never a good idea.</description>
		<content:encoded><![CDATA[<p>Yes, you *can* overcommit memory and have things be fine up until that memory is actually addressed and the machine starts to swap to disk. That&#8217;s when things get dirty. If you need to allocate that much ram to your buffers you&#8217;re better off installing 64GB of ram. Overcommitting memory is never a good idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://themattreid.com/wordpress/2009/04/28/a-quick-rundown-of-per-thread-buffers/comment-page-1/#comment-80</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 30 Apr 2009 08:52:02 +0000</pubDate>
		<guid isPermaLink="false">http://themattreid.com/wordpress/?p=157#comment-80</guid>
		<description>Hi Matt.

Actually, you can overcommit memory with read_buffer_size and sort_buffer_size and usually have no problems. I have worked on large systems with physical RAM of 16 GB and formula = 64 GB just fine. And
those are MyISAM-specific.

Also, not sure if read_buffer and read_buffer_size are the same. I believe they are not.

Also see this blog post:
http://www.mysqlperformanceblog.com/2006/05/17/mysql-server-memory-usage/

James.</description>
		<content:encoded><![CDATA[<p>Hi Matt.</p>
<p>Actually, you can overcommit memory with read_buffer_size and sort_buffer_size and usually have no problems. I have worked on large systems with physical RAM of 16 GB and formula = 64 GB just fine. And<br />
those are MyISAM-specific.</p>
<p>Also, not sure if read_buffer and read_buffer_size are the same. I believe they are not.</p>
<p>Also see this blog post:<br />
<a href="http://www.mysqlperformanceblog.com/2006/05/17/mysql-server-memory-usage/" rel="nofollow">http://www.mysqlperformanceblog.com/2006/05/17/mysql-server-memory-usage/</a></p>
<p>James.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

