<?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: Measuring what matters</title>
	<atom:link href="http://blog.tanelpoder.com/2009/12/22/measuring-what-matters/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tanelpoder.com/2009/12/22/measuring-what-matters/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=measuring-what-matters</link>
	<description>Oracle, Exadata, Performance, Troubleshooting - Mobile Life and Productivity.</description>
	<lastBuildDate>Wed, 08 Feb 2012 08:03:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tanel Poder</title>
		<link>http://blog.tanelpoder.com/2009/12/22/measuring-what-matters/comment-page-1/#comment-3468</link>
		<dc:creator>Tanel Poder</dc:creator>
		<pubDate>Sat, 26 Dec 2009 04:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tanelpoder.com/?p=511#comment-3468</guid>
		<description>If your question is that how to determine whether we are using too much of computing resources for a business transaction - there&#039;s no single answer there, especially considering that there are many crappy (3rd party) applications out there which are inefficient by design!

However the principle (too much work or too much waiting) still applies at all levels of troubleshooting/performance optimization.

I intend to write many articles on this topic!</description>
		<content:encoded><![CDATA[<p>If your question is that how to determine whether we are using too much of computing resources for a business transaction &#8211; there&#8217;s no single answer there, especially considering that there are many crappy (3rd party) applications out there which are inefficient by design!</p>
<p>However the principle (too much work or too much waiting) still applies at all levels of troubleshooting/performance optimization.</p>
<p>I intend to write many articles on this topic!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Narendra</title>
		<link>http://blog.tanelpoder.com/2009/12/22/measuring-what-matters/comment-page-1/#comment-3463</link>
		<dc:creator>Narendra</dc:creator>
		<pubDate>Thu, 24 Dec 2009 10:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tanelpoder.com/?p=511#comment-3463</guid>
		<description>Tanel,

Nice summary. While I am not a professional consultant, I have come across some situations where the following is applicable:
=====================================
    * Your response times are too long for only two reasons:

       1. You are doing too much work
=====================================

But how do you decide when the available hardware resources are simply insufficient for the amount of work being done?</description>
		<content:encoded><![CDATA[<p>Tanel,</p>
<p>Nice summary. While I am not a professional consultant, I have come across some situations where the following is applicable:<br />
=====================================<br />
    * Your response times are too long for only two reasons:</p>
<p>       1. You are doing too much work<br />
=====================================</p>
<p>But how do you decide when the available hardware resources are simply insufficient for the amount of work being done?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

