<?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: What do we optimize with mk-query-digest ?</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2009/12/15/what-do-we-optimize-with-mk-query-digest/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2009/12/15/what-do-we-optimize-with-mk-query-digest/</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: peter</title>
		<link>http://www.mysqlperformanceblog.com/2009/12/15/what-do-we-optimize-with-mk-query-digest/comment-page-1/#comment-697594</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Thu, 17 Dec 2009 15:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1924#comment-697594</guid>
		<description>Dalin,

Right. You&#039;ve got to check your pages with YSlow as well.  People often confront me with these 15% numbers quoting Steve Sounders  and as with any general number it is oversimplification.    The number applies to the cases when backend is well optimized already.  If you have HTML generated in 100ms  it is quite likely you&#039;ve got to invest in Front End optimization first. However if you have backend performing very badly - think 30 seconds to load the page, or even time out all together  the distribution is going to be completely broken.

The &quot;right&quot; approach is of course to start from the top and go to the bottom - if HTML is leading contributer to client response time you optimize it, else focus on other things.</description>
		<content:encoded><![CDATA[<p>Dalin,</p>
<p>Right. You&#8217;ve got to check your pages with YSlow as well.  People often confront me with these 15% numbers quoting Steve Sounders  and as with any general number it is oversimplification.    The number applies to the cases when backend is well optimized already.  If you have HTML generated in 100ms  it is quite likely you&#8217;ve got to invest in Front End optimization first. However if you have backend performing very badly &#8211; think 30 seconds to load the page, or even time out all together  the distribution is going to be completely broken.</p>
<p>The &#8220;right&#8221; approach is of course to start from the top and go to the bottom &#8211; if HTML is leading contributer to client response time you optimize it, else focus on other things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dalin</title>
		<link>http://www.mysqlperformanceblog.com/2009/12/15/what-do-we-optimize-with-mk-query-digest/comment-page-1/#comment-697317</link>
		<dc:creator>dalin</dc:creator>
		<pubDate>Thu, 17 Dec 2009 06:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=1924#comment-697317</guid>
		<description>And if improving user interaction response times in a web site/application is what you are wanting, then you need to know that only ~15% of time is spent generating the HTML page and getting it to the client.  The rest is things like transfering images, CSS, and JavaScript.  If you haven&#039;t yet, get YSlow and Google Page Speed and analyze your front-end performance.</description>
		<content:encoded><![CDATA[<p>And if improving user interaction response times in a web site/application is what you are wanting, then you need to know that only ~15% of time is spent generating the HTML page and getting it to the client.  The rest is things like transfering images, CSS, and JavaScript.  If you haven&#8217;t yet, get YSlow and Google Page Speed and analyze your front-end performance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

