<?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: iTunes pegged my CPU at over 130%?</title>
	<atom:link href="http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/feed/" rel="self" type="application/rss+xml" />
	<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/</link>
	<description>the personal blog of Stuart Colville covering modern web development techniques and best practices</description>
	<pubDate>Thu, 20 Nov 2008 10:02:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Mark</title>
		<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-63625</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 18 Oct 2007 12:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-63625</guid>
		<description>I have a single core processor (G3 800MHz), and I'm seeing top reporting iTunes using CPU of up to 124%. this is with OSX 10.4. Any ideas why that would be?</description>
		<content:encoded><![CDATA[<p>I have a single core processor (G3 800MHz), and I&#8217;m seeing top reporting iTunes using CPU of up to 124%. this is with OSX 10.4. Any ideas why that would be?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Colville</title>
		<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11347</link>
		<dc:creator>Stuart Colville</dc:creator>
		<pubDate>Thu, 05 Oct 2006 07:58:54 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11347</guid>
		<description>@Feaverish, Mackie, Johan, David: Had to be didn't it. Though it would be nice if top reported only up to 100% for a dual core CPU as that would make more sense &lt;acronym title="In My Humble Opinion"&gt;imho&lt;/acronym&gt;.

@Christian: Quite probably!</description>
		<content:encoded><![CDATA[<p>@Feaverish, Mackie, Johan, David: Had to be didn&#8217;t it. Though it would be nice if top reported only up to 100% for a dual core CPU as that would make more sense <acronym title="In My Humble Opinion">imho</acronym>.</p>
<p>@Christian: Quite probably!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Emery</title>
		<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11343</link>
		<dc:creator>David Emery</dc:creator>
		<pubDate>Thu, 05 Oct 2006 07:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11343</guid>
		<description>As you've got a dual processor system, and iTunes is multi-threded, the number can indeed go above 100% - you have 200% to play with.</description>
		<content:encoded><![CDATA[<p>As you&#8217;ve got a dual processor system, and iTunes is multi-threded, the number can indeed go above 100% - you have 200% to play with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan M</title>
		<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11342</link>
		<dc:creator>Johan M</dc:creator>
		<pubDate>Thu, 05 Oct 2006 06:54:24 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11342</guid>
		<description>The CPU load maximum is per processor (or core). Since your MacBook Pro has two cores, the maximum is 200%.</description>
		<content:encoded><![CDATA[<p>The CPU load maximum is per processor (or core). Since your MacBook Pro has two cores, the maximum is 200%.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Heilmann</title>
		<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11338</link>
		<dc:creator>Chris Heilmann</dc:creator>
		<pubDate>Thu, 05 Oct 2006 06:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11338</guid>
		<description>My guess is that the CPU blushed at the sight of what you store on the iPod. This caused more heating and the system read this as more processing. That's where the wrong number came from.</description>
		<content:encoded><![CDATA[<p>My guess is that the CPU blushed at the sight of what you store on the iPod. This caused more heating and the system read this as more processing. That&#8217;s where the wrong number came from.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mackie</title>
		<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11328</link>
		<dc:creator>Mackie</dc:creator>
		<pubDate>Thu, 05 Oct 2006 03:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11328</guid>
		<description>Apparently with dual processors you can go up to 200%. I found this out after I bought my first dual processor Mac four years ago, and imported lots of things at once in iTunes.</description>
		<content:encoded><![CDATA[<p>Apparently with dual processors you can go up to 200%. I found this out after I bought my first dual processor Mac four years ago, and imported lots of things at once in iTunes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Feaverish</title>
		<link>http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11318</link>
		<dc:creator>Feaverish</dc:creator>
		<pubDate>Thu, 05 Oct 2006 01:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://muffinresearch.co.uk/archives/2006/10/04/itunes-pegged-my-cpu-at-over-130/#comment-11318</guid>
		<description>With two cores (or processors) you can get up to 200%. A lot of system monitors (MenuMeters, et al.) average the processor loads and only output up to 100% (which would mean both cores are pegged at 100%, for 200% total).</description>
		<content:encoded><![CDATA[<p>With two cores (or processors) you can get up to 200%. A lot of system monitors (MenuMeters, et al.) average the processor loads and only output up to 100% (which would mean both cores are pegged at 100%, for 200% total).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
