<?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: On Good Instrumentation</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2010/05/31/on-good-instrumentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2010/05/31/on-good-instrumentation/</link>
	<description>Percona&#039;s MySQL &#38; InnoDB performance and scalability blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Stefan</title>
		<link>http://www.mysqlperformanceblog.com/2010/05/31/on-good-instrumentation/comment-page-1/#comment-765943</link>
		<dc:creator>Stefan</dc:creator>
		<pubDate>Tue, 01 Jun 2010 10:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=2912#comment-765943</guid>
		<description>I&#039;m happily using in-memory tracking of percentiles along with some neat Google charts to get a very quick impression of response times at several layers. Here&#039;s a writeup and some (pretty efficient) Java code for anybody interested: http://techblog.molindo.at/2009/11/efficiently-tracking-response-time-percentiles.html</description>
		<content:encoded><![CDATA[<p>I&#8217;m happily using in-memory tracking of percentiles along with some neat Google charts to get a very quick impression of response times at several layers. Here&#8217;s a writeup and some (pretty efficient) Java code for anybody interested: <a href="http://techblog.molindo.at/2009/11/efficiently-tracking-response-time-percentiles.html" rel="nofollow">http://techblog.molindo.at/2009/11/efficiently-tracking-response-time-percentiles.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

