<?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: Beware: key_buffer_size larger than 4G does not work</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mysql-d</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-490133</link>
		<dc:creator>mysql-d</dc:creator>
		<pubDate>Thu, 26 Feb 2009 10:29:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-490133</guid>
		<description>I think the issues is not with mysql but the file system that is been provided by the operating system.

The EXT 2 file system just provides with 4 Gigs of max file size support. I think you should try with the EXT 3 file system 
which is more thatn lots and lots of terabites

Thanks</description>
		<content:encoded><![CDATA[<p>I think the issues is not with mysql but the file system that is been provided by the operating system.</p>
<p>The EXT 2 file system just provides with 4 Gigs of max file size support. I think you should try with the EXT 3 file system<br />
which is more thatn lots and lots of terabites</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Przemek</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-357109</link>
		<dc:creator>Przemek</dc:creator>
		<pubDate>Mon, 22 Sep 2008 10:11:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-357109</guid>
		<description>As of MySQL 5.0.52, values larger than 4GB are allowed for 64-bit platforms (except 64-bit Windows).</description>
		<content:encoded><![CDATA[<p>As of MySQL 5.0.52, values larger than 4GB are allowed for 64-bit platforms (except 64-bit Windows).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David W. Juntgen</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-114277</link>
		<dc:creator>David W. Juntgen</dc:creator>
		<pubDate>Thu, 26 Apr 2007 04:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-114277</guid>
		<description>Currently all version of MySQL have a limit to the max size of the key_buffer_size, which is set to 4G.

http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html

But...there are ways around this limitation, you can add additional key buffers or (CACHE INDEXs) for individual tables after the server starts.  You can read about this more here: 

http://dev.mysql.com/doc/refman/5.0/en/multiple-key-caches.html

Later!

--Dave</description>
		<content:encoded><![CDATA[<p>Currently all version of MySQL have a limit to the max size of the key_buffer_size, which is set to 4G.</p>
<p><a href="http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html</a></p>
<p>But&#8230;there are ways around this limitation, you can add additional key buffers or (CACHE INDEXs) for individual tables after the server starts.  You can read about this more here: </p>
<p><a href="http://dev.mysql.com/doc/refman/5.0/en/multiple-key-caches.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.0/en/multiple-key-caches.html</a></p>
<p>Later!</p>
<p>&#8211;Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Nuriyev</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-109888</link>
		<dc:creator>Daniel Nuriyev</dc:creator>
		<pubDate>Tue, 17 Apr 2007 16:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-109888</guid>
		<description>I have 8Gb RAM with MySQL 5.0.27. Mistakingly I set key_buffer_size to 20Gb instead of 2Gb. Then I opened MySQL Administrator Health tab and saw there 4Gb of key_buffer_size. It seems that MySQL has some code that makes sure that key_buffer_size will not be more than the maximum.
Note: I set key_buffer_size through SET GLOBAL key_buffer_size = ...; SQL command. I did not do it through a configuration file.</description>
		<content:encoded><![CDATA[<p>I have 8Gb RAM with MySQL 5.0.27. Mistakingly I set key_buffer_size to 20Gb instead of 2Gb. Then I opened MySQL Administrator Health tab and saw there 4Gb of key_buffer_size. It seems that MySQL has some code that makes sure that key_buffer_size will not be more than the maximum.<br />
Note: I set key_buffer_size through SET GLOBAL key_buffer_size = &#8230;; SQL command. I did not do it through a configuration file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David W. Juntgen</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-89653</link>
		<dc:creator>David W. Juntgen</dc:creator>
		<pubDate>Mon, 19 Mar 2007 22:26:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-89653</guid>
		<description>Peter,

If you would like to force mysql to lock itself into memory you can.  This is useful to avoid page swaping.  The down fall is that you must run as root and it sucks up all the memory defined by your my.cnf file for MyISAM and Innodb buffer pools.  So, if you have a 6G key buffer, then you top will show a RES of 6G.

In your my.cnf file add these two lines under [mysqld]

user=root
memlock

--David</description>
		<content:encoded><![CDATA[<p>Peter,</p>
<p>If you would like to force mysql to lock itself into memory you can.  This is useful to avoid page swaping.  The down fall is that you must run as root and it sucks up all the memory defined by your my.cnf file for MyISAM and Innodb buffer pools.  So, if you have a 6G key buffer, then you top will show a RES of 6G.</p>
<p>In your my.cnf file add these two lines under [mysqld]</p>
<p>user=root<br />
memlock</p>
<p>&#8211;David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sean</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-83044</link>
		<dc:creator>sean</dc:creator>
		<pubDate>Wed, 14 Mar 2007 23:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-83044</guid>
		<description>Peter,
Is there a way to monitor the usage and efficency of multiple key caches?  Perhaps something similar &#039;key_reads&#039; and &#039;key_read_requests&#039;.</description>
		<content:encoded><![CDATA[<p>Peter,<br />
Is there a way to monitor the usage and efficency of multiple key caches?  Perhaps something similar &#8216;key_reads&#8217; and &#8216;key_read_requests&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-60409</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Sun, 25 Feb 2007 20:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-60409</guid>
		<description>Sean,  As you found out yourself, yes this is the workaround you can use :)</description>
		<content:encoded><![CDATA[<p>Sean,  As you found out yourself, yes this is the workaround you can use <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-60386</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Sun, 25 Feb 2007 20:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-60386</guid>
		<description>My bad Peter, didn&#039;t see your comment above :(</description>
		<content:encoded><![CDATA[<p>My bad Peter, didn&#8217;t see your comment above <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-60382</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Sun, 25 Feb 2007 20:22:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-60382</guid>
		<description>Peter,

Though I haven&#039;t tried it, can one create multiple key caches up to 4 GB of memory as a work around?</description>
		<content:encoded><![CDATA[<p>Peter,</p>
<p>Though I haven&#8217;t tried it, can one create multiple key caches up to 4 GB of memory as a work around?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An Expert's Guide to Oracle Technology</title>
		<link>http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/comment-page-1/#comment-52799</link>
		<dc:creator>An Expert's Guide to Oracle Technology</dc:creator>
		<pubDate>Fri, 16 Feb 2007 16:56:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2007/02/14/beware-key_buffer_size-larger-than-4g-does-not-work/#comment-52799</guid>
		<description>&lt;strong&gt;Log Buffer #32: a Carnival of the Vanities for DBAs...&lt;/strong&gt;

Welcome, to the 32nd edition of Log Buffer, the weekly survey of database blogs. What shall I talk about? Hmmm, maybe I&#039;ll start with the Oracle blogosphere. Might as well get started with controversy by reading an entry by Dean......</description>
		<content:encoded><![CDATA[<p><strong>Log Buffer #32: a Carnival of the Vanities for DBAs&#8230;</strong></p>
<p>Welcome, to the 32nd edition of Log Buffer, the weekly survey of database blogs. What shall I talk about? Hmmm, maybe I&#8217;ll start with the Oracle blogosphere. Might as well get started with controversy by reading an entry by Dean&#8230;&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
