<?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"
	>
<channel>
	<title>Comments on: Load Average</title>
	<atom:link href="http://etbe.coker.com.au/2007/11/01/load-average/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au/2007/11/01/load-average/</link>
	<description>Linux, politics, and other interesting things</description>
	<pubDate>Sat, 11 Oct 2008 01:58:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: etbe</title>
		<link>http://etbe.coker.com.au/2007/11/01/load-average/#comment-10191</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Tue, 06 Nov 2007 21:17:24 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/2007/11/01/load-average/#comment-10191</guid>
		<description>Peter:  Good point.  I will add an item to my todo list to write more about this.</description>
		<content:encoded><![CDATA[<p>Peter:  Good point.  I will add an item to my todo list to write more about this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Moulder</title>
		<link>http://etbe.coker.com.au/2007/11/01/load-average/#comment-10169</link>
		<dc:creator>Peter Moulder</dc:creator>
		<pubDate>Tue, 06 Nov 2007 13:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/2007/11/01/load-average/#comment-10169</guid>
		<description>Incidentally, the traditional description of “average over the last 1, 5 and 15 minutes” is really a piece of fiction, at least regarding Linux.  They're exponentially smoothed values, and they don't really correspond to “1 minute” or whatever in any meaningful way that I know of; e.g. the smoothing values chosen don't minimize the sum of (absolute or squared or cubed or ^1.1) differences between the exponentially smoothed value and the true 1 minute (etc.) moving average.  The only meaningfulness that I know of for the expression used to calculate the smoothing value in Linux (viz. 1/exp((update interval)/{1,5,15}min)) is that at least the ratio 1:5:15 is meaningful, even if the absolute time durations aren't.  I'd be interested to hear if someone knows why that expression was chosen, or why it's useful to use that expression rather than one that gives a value closer to the 1min moving average.</description>
		<content:encoded><![CDATA[<p>Incidentally, the traditional description of “average over the last 1, 5 and 15 minutes” is really a piece of fiction, at least regarding Linux.  They&#8217;re exponentially smoothed values, and they don&#8217;t really correspond to “1 minute” or whatever in any meaningful way that I know of; e.g. the smoothing values chosen don&#8217;t minimize the sum of (absolute or squared or cubed or ^1.1) differences between the exponentially smoothed value and the true 1 minute (etc.) moving average.  The only meaningfulness that I know of for the expression used to calculate the smoothing value in Linux (viz. 1/exp((update interval)/{1,5,15}min)) is that at least the ratio 1:5:15 is meaningful, even if the absolute time durations aren&#8217;t.  I&#8217;d be interested to hear if someone knows why that expression was chosen, or why it&#8217;s useful to use that expression rather than one that gives a value closer to the 1min moving average.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: etbe</title>
		<link>http://etbe.coker.com.au/2007/11/01/load-average/#comment-9950</link>
		<dc:creator>etbe</dc:creator>
		<pubDate>Fri, 02 Nov 2007 21:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/2007/11/01/load-average/#comment-9950</guid>
		<description>The disks in question are a year old and were not particularly fast when I bought them.  Doubling the performance is quite possible.

iostat does display what it considers to be the disk usage percentage, not sure how accurate it is - I know that the 0% and 100% values are right though.  ;)</description>
		<content:encoded><![CDATA[<p>The disks in question are a year old and were not particularly fast when I bought them.  Doubling the performance is quite possible.</p>
<p>iostat does display what it considers to be the disk usage percentage, not sure how accurate it is - I know that the 0% and 100% values are right though.  ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olaf van der Spek</title>
		<link>http://etbe.coker.com.au/2007/11/01/load-average/#comment-9922</link>
		<dc:creator>Olaf van der Spek</dc:creator>
		<pubDate>Fri, 02 Nov 2007 12:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/2007/11/01/load-average/#comment-9922</guid>
		<description>BTW, why is there no simple disk usage metric? Like, this disk is busy 50% of the time.</description>
		<content:encoded><![CDATA[<p>BTW, why is there no simple disk usage metric? Like, this disk is busy 50% of the time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olaf van der Spek</title>
		<link>http://etbe.coker.com.au/2007/11/01/load-average/#comment-9921</link>
		<dc:creator>Olaf van der Spek</dc:creator>
		<pubDate>Fri, 02 Nov 2007 12:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/2007/11/01/load-average/#comment-9921</guid>
		<description>&#62; But if the disk IO performance was doubled (a realistic possibility given that the system has a pair of cheap SATA disks in a RAID-1) then find would probably use 8% of CPU time.

Doubling STR does still not (always) double performance. ;)</description>
		<content:encoded><![CDATA[<p>&gt; But if the disk IO performance was doubled (a realistic possibility given that the system has a pair of cheap SATA disks in a RAID-1) then find would probably use 8% of CPU time.</p>
<p>Doubling STR does still not (always) double performance. ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
