<?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: Thank you for the MySQL 5.4 Community Release</title>
	<atom:link href="http://www.xaprb.com/blog/2009/04/25/thank-you-for-the-mysql-54-community-release/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xaprb.com/blog/2009/04/25/thank-you-for-the-mysql-54-community-release/</link>
	<description>Stay curious!</description>
	<lastBuildDate>Thu, 09 Feb 2012 09:56:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mark Callaghan</title>
		<link>http://www.xaprb.com/blog/2009/04/25/thank-you-for-the-mysql-54-community-release/#comment-16394</link>
		<dc:creator>Mark Callaghan</dc:creator>
		<pubDate>Mon, 04 May 2009 13:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1028#comment-16394</guid>
		<description>Have I read this correctly?

From http://forge.mysql.com/worklog/task.php?id=4895 they will generate events for every row operation and then from http://forge.mysql.com/worklog/task.php?id=4816 support will eventually be added for summary tables.

I want the summary tables first. I am skeptical that the per-event instrumentation can be done without a lot of CPU overhead. It will certainly have a lot of memory overhead to buffer events. And I want to have stats enabled all of the time for the summary tables.</description>
		<content:encoded><![CDATA[<p>Have I read this correctly?</p>
<p>From <a href="http://forge.mysql.com/worklog/task.php?id=4895" rel="nofollow">http://forge.mysql.com/worklog/task.php?id=4895</a> they will generate events for every row operation and then from <a href="http://forge.mysql.com/worklog/task.php?id=4816" rel="nofollow">http://forge.mysql.com/worklog/task.php?id=4816</a> support will eventually be added for summary tables.</p>
<p>I want the summary tables first. I am skeptical that the per-event instrumentation can be done without a lot of CPU overhead. It will certainly have a lot of memory overhead to buffer events. And I want to have stats enabled all of the time for the summary tables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Leith</title>
		<link>http://www.xaprb.com/blog/2009/04/25/thank-you-for-the-mysql-54-community-release/#comment-16375</link>
		<dc:creator>Mark Leith</dc:creator>
		<pubDate>Fri, 01 May 2009 09:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1028#comment-16375</guid>
		<description>Hey Mark,

Yea, we know you want that pretty bad. :) 

We currently have this worklog for looking at table/object usage:

http://forge.mysql.com/worklog/task.php?id=4895

Would this fit your needs for table monitoring? 

Many of the core developers (Serg, Kostja, et al) are pretty keen to see the object monitoring rather than file IO as well, so there&#039;s a lot of push to get this in there as well from inside too. 

Vote on the worklog if it fits your needs! :)</description>
		<content:encoded><![CDATA[<p>Hey Mark,</p>
<p>Yea, we know you want that pretty bad. :) </p>
<p>We currently have this worklog for looking at table/object usage:</p>
<p><a href="http://forge.mysql.com/worklog/task.php?id=4895" rel="nofollow">http://forge.mysql.com/worklog/task.php?id=4895</a></p>
<p>Would this fit your needs for table monitoring? </p>
<p>Many of the core developers (Serg, Kostja, et al) are pretty keen to see the object monitoring rather than file IO as well, so there&#8217;s a lot of push to get this in there as well from inside too. </p>
<p>Vote on the worklog if it fits your needs! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Callaghan</title>
		<link>http://www.xaprb.com/blog/2009/04/25/thank-you-for-the-mysql-54-community-release/#comment-16371</link>
		<dc:creator>Mark Callaghan</dc:creator>
		<pubDate>Fri, 01 May 2009 01:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1028#comment-16371</guid>
		<description>We need the IO performance changes for InnoDB from the Percona and Google patches. 5.4 has support for more background IO threads, but a lot of work has been done in the last 6 months to make things much better.

It would be nice to know that performance stats aggregated by user and table are in the performance schema roadmap.</description>
		<content:encoded><![CDATA[<p>We need the IO performance changes for InnoDB from the Percona and Google patches. 5.4 has support for more background IO threads, but a lot of work has been done in the last 6 months to make things much better.</p>
<p>It would be nice to know that performance stats aggregated by user and table are in the performance schema roadmap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt&#8217;s Blog &#187; Blog Archive &#187; Link Roundup</title>
		<link>http://www.xaprb.com/blog/2009/04/25/thank-you-for-the-mysql-54-community-release/#comment-16370</link>
		<dc:creator>Matt&#8217;s Blog &#187; Blog Archive &#187; Link Roundup</dc:creator>
		<pubDate>Fri, 01 May 2009 00:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1028#comment-16370</guid>
		<description>[...] is a little bit baffled, but Xapbr posts a Thank You for MySQL 5.4 Community. I think the baffling is due to several things: (1) There wasn&#8217;t much talk about MySQL 5.4 as [...]</description>
		<content:encoded><![CDATA[<p>[...] is a little bit baffled, but Xapbr posts a Thank You for MySQL 5.4 Community. I think the baffling is due to several things: (1) There wasn&#8217;t much talk about MySQL 5.4 as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Leith</title>
		<link>http://www.xaprb.com/blog/2009/04/25/thank-you-for-the-mysql-54-community-release/#comment-16341</link>
		<dc:creator>Mark Leith</dc:creator>
		<pubDate>Tue, 28 Apr 2009 13:10:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/?p=1028#comment-16341</guid>
		<description>Oh I agree of course, and we&#039;re working hard to open up to the community as well (http://blogs.sun.com/datacharmer/entry/the_pursuit_of_openness).

What else would you guys need, to be able to start feeding back patches? There&#039;s some great stuff in there, I think it&#039;s a real shame that the &quot;wider community&quot; misses out, and would love to see you guys working closer with us now that we are trying to open up with such vigor.</description>
		<content:encoded><![CDATA[<p>Oh I agree of course, and we&#8217;re working hard to open up to the community as well (<a href="http://blogs.sun.com/datacharmer/entry/the_pursuit_of_openness" rel="nofollow">http://blogs.sun.com/datacharmer/entry/the_pursuit_of_openness</a>).</p>
<p>What else would you guys need, to be able to start feeding back patches? There&#8217;s some great stuff in there, I think it&#8217;s a real shame that the &#8220;wider community&#8221; misses out, and would love to see you guys working closer with us now that we are trying to open up with such vigor.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

