<?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: processor load</title>
	<atom:link href="http://www.coriolinus.net/2010/01/16/processor-load/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coriolinus.net/2010/01/16/processor-load/</link>
	<description>read, and be entertained</description>
	<lastBuildDate>Thu, 16 Jun 2011 07:31:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: coriolinus</title>
		<link>http://www.coriolinus.net/2010/01/16/processor-load/comment-page-1/#comment-38139</link>
		<dc:creator>coriolinus</dc:creator>
		<pubDate>Tue, 26 Jan 2010 08:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.coriolinus.net/?p=2959#comment-38139</guid>
		<description>I liked it when I tried it, but I&#039;ve got a number of extensions that I&#039;m quite fond of and I suspect I&#039;d be annoyed trying to track down analogs.</description>
		<content:encoded><![CDATA[<p>I liked it when I tried it, but I&#8217;ve got a number of extensions that I&#8217;m quite fond of and I suspect I&#8217;d be annoyed trying to track down analogs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: coriolinus</title>
		<link>http://www.coriolinus.net/2010/01/16/processor-load/comment-page-1/#comment-38055</link>
		<dc:creator>coriolinus</dc:creator>
		<pubDate>Thu, 21 Jan 2010 14:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.coriolinus.net/?p=2959#comment-38055</guid>
		<description>That makes sense in your use case, but I don&#039;t have my FF save that data; I start each new session with just the one default tab. Further compounding the issue is that when I close it, it &lt;em&gt;vanishes&lt;/em&gt; instantly; it just takes significant realtime for the process to die. I only noticed the behavior because I&#039;m absent-minded, and fairly often kill the browser only to remember a second later a link I wanted to visit. To do that, I have to manually kill the process or wait for it to time out.

I&#039;d suspect it was extension-related behavior but I have only one extension that&#039;s supposed to do work on shutdown and it didn&#039;t cause comparable problems on my older machine.</description>
		<content:encoded><![CDATA[<p>That makes sense in your use case, but I don&#8217;t have my FF save that data; I start each new session with just the one default tab. Further compounding the issue is that when I close it, it <em>vanishes</em> instantly; it just takes significant realtime for the process to die. I only noticed the behavior because I&#8217;m absent-minded, and fairly often kill the browser only to remember a second later a link I wanted to visit. To do that, I have to manually kill the process or wait for it to time out.</p>
<p>I&#8217;d suspect it was extension-related behavior but I have only one extension that&#8217;s supposed to do work on shutdown and it didn&#8217;t cause comparable problems on my older machine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dad</title>
		<link>http://www.coriolinus.net/2010/01/16/processor-load/comment-page-1/#comment-38021</link>
		<dc:creator>Dad</dc:creator>
		<pubDate>Mon, 18 Jan 2010 13:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.coriolinus.net/?p=2959#comment-38021</guid>
		<description>I&#039;ve asked Firefox to save my current windows + tabs on shutdown, and restore on startup. So I tend to accumulate FF windows + tabs. At last count I have something like 128 tabs distributed over 9 windows -- but that was a few weeks ago. I&#039;m not sure in what direction it&#039;s varied since then.

It takes my FF significant realtime to shut down, but that&#039;s not mysterious to me at all. I&#039;m guessing that, quite aside from the time to actually serialize the key data, I&#039;m seeing ~128 different threads queueing for some kind of lock to gain the right to talk to the appropriate file(s).

Your observation might suggest a spin lock that keeps the processors busy until granted.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve asked Firefox to save my current windows + tabs on shutdown, and restore on startup. So I tend to accumulate FF windows + tabs. At last count I have something like 128 tabs distributed over 9 windows &#8212; but that was a few weeks ago. I&#8217;m not sure in what direction it&#8217;s varied since then.</p>
<p>It takes my FF significant realtime to shut down, but that&#8217;s not mysterious to me at all. I&#8217;m guessing that, quite aside from the time to actually serialize the key data, I&#8217;m seeing ~128 different threads queueing for some kind of lock to gain the right to talk to the appropriate file(s).</p>
<p>Your observation might suggest a spin lock that keeps the processors busy until granted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.coriolinus.net/2010/01/16/processor-load/comment-page-1/#comment-38011</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 17 Jan 2010 16:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.coriolinus.net/?p=2959#comment-38011</guid>
		<description>Firefox can be extremely frustrating when it comes to things like this.  I&#039;m starting to use Google Chrome when I can, it seems to be a better browser though not as mature.</description>
		<content:encoded><![CDATA[<p>Firefox can be extremely frustrating when it comes to things like this.  I&#8217;m starting to use Google Chrome when I can, it seems to be a better browser though not as mature.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

