<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: burning cpu and battery on the gnome desktop</title>
	<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/</link>
	<description>a lowercase manifesto</description>
	<pubDate>Sun, 07 Sep 2008 22:06:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Quim Gil</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-53</link>
		<dc:creator>Quim Gil</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-53</guid>
		<description>Ryan, one of my best discoveries of this GUADEC!&lt;p/&gt;I'm no performance expert at all, just another user suggering the effects of non-optimized performance in my laptop. I like to read posts like this one of yours, though. Like I enjoy reading Ben Maurer's or Federico's. &lt;p/&gt;Compared to releasing cool new features, optimization could be seen as a pretty boring and unnoticed effort. But you're my heroes! Keep the good work going.&lt;p/&gt;A happier user.</description>
		<content:encoded><![CDATA[<p>Ryan, one of my best discoveries of this GUADEC!
<p />I&#8217;m no performance expert at all, just another user suggering the effects of non-optimized performance in my laptop. I like to read posts like this one of yours, though. Like I enjoy reading Ben Maurer&#8217;s or Federico&#8217;s.
<p />Compared to releasing cool new features, optimization could be seen as a pretty boring and unnoticed effort. But you&#8217;re my heroes! Keep the good work going.
<p />A happier user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emmanuel</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-54</link>
		<dc:creator>emmanuel</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-54</guid>
		<description>this work is appreciated. performance is the thing were GNOME needs the most love right now... it's great that GNOME came that far!</description>
		<content:encoded><![CDATA[<p>this work is appreciated. performance is the thing were GNOME needs the most love right now&#8230; it&#8217;s great that GNOME came that far!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wade Menard</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-55</link>
		<dc:creator>Wade Menard</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-55</guid>
		<description>I haven't looked at the code but clock-applet is probably using the same ~1s timer to reduce delay in updating the minutes. Perhaps it could sync up to the next minute update then switch to a 60s sleep?</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t looked at the code but clock-applet is probably using the same ~1s timer to reduce delay in updating the minutes. Perhaps it could sync up to the next minute update then switch to a 60s sleep?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Dowland</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-56</link>
		<dc:creator>Jon Dowland</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-56</guid>
		<description>Thanks for this post. I shall keep this list and look out for the patches :)&lt;p/&gt;I tried stracing a very trivial GLADE-powered application I wrote (in ruby). It is going through an ioctl/gettimeofday/select loop when idle. The code I have written is so trivial, I'm thinking that there must be some bad stuff in either ruby or glade.</description>
		<content:encoded><![CDATA[<p>Thanks for this post. I shall keep this list and look out for the patches :)
<p />I tried stracing a very trivial GLADE-powered application I wrote (in ruby). It is going through an ioctl/gettimeofday/select loop when idle. The code I have written is so trivial, I&#8217;m thinking that there must be some bad stuff in either ruby or glade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Wingo</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-57</link>
		<dc:creator>Andy Wingo</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-57</guid>
		<description>Nice testing :)</description>
		<content:encoded><![CDATA[<p>Nice testing :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mkv</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-58</link>
		<dc:creator>mkv</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-58</guid>
		<description>Excellent work! This kind of info and optimization is also probably going to be vital to the olpc effort.</description>
		<content:encoded><![CDATA[<p>Excellent work! This kind of info and optimization is also probably going to be vital to the olpc effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leen Toelen</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-59</link>
		<dc:creator>Leen Toelen</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-59</guid>
		<description>For debugging these things, you should aybe give dtrace on opensolaris a try.&lt;p/&gt;Nice work!</description>
		<content:encoded><![CDATA[<p>For debugging these things, you should aybe give dtrace on opensolaris a try.
<p />Nice work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nelson</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-60</link>
		<dc:creator>Nelson</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-60</guid>
		<description>Great analysis!, I hope this post becomes a future GnomeGoal or SoC project, because these small(in appearance) details do really make a difference in the long term and wrt other desktops.</description>
		<content:encoded><![CDATA[<p>Great analysis!, I hope this post becomes a future GnomeGoal or SoC project, because these small(in appearance) details do really make a difference in the long term and wrt other desktops.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kiddo</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-61</link>
		<dc:creator>Kiddo</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-61</guid>
		<description>I'm amazed to see such good work going into optimization for GNOME, keep it up! :)&lt;p/&gt;Out of curiosity, I tried stracing specto, and I don't know how I should interpret the result. This application uses gobject timers to determine when to check for updates. I have thousands of lines like this scrolling up, because it seems to calculate the unix time all the time:&lt;p/&gt;ioctl(15, FIONREAD, [0])                = 0&lt;br/&gt;gettimeofday({1154014114, 834950}, NULL) = 0&lt;p/&gt;&lt;br/&gt;Should I be worried, or this is just plain normal? I noticed gaim has those, but MUCH less frequently.</description>
		<content:encoded><![CDATA[<p>I&#8217;m amazed to see such good work going into optimization for GNOME, keep it up! :)
<p />Out of curiosity, I tried stracing specto, and I don&#8217;t know how I should interpret the result. This application uses gobject timers to determine when to check for updates. I have thousands of lines like this scrolling up, because it seems to calculate the unix time all the time:
<p />ioctl(15, FIONREAD, [0])                = 0<br />gettimeofday({1154014114, 834950}, NULL) = 0
<p />Should I be worried, or this is just plain normal? I noticed gaim has those, but MUCH less frequently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: desrt</title>
		<link>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-62</link>
		<dc:creator>desrt</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid>http://blogs.gnome.org/desrt/2006/07/27/burning-cpu-and-battery-on-the-gnome-desktop/#comment-62</guid>
		<description>kiddo; if you see lines after lines of those two things (without a poll, sleep, select, etc) in between them then you have trouble indeed.  this means that your application is running in an infinite loop and never sleeping at all (ie: is pegging the cpu at 100%).&lt;p/&gt;unless your app is actively doing work it shouldn't be doing this.</description>
		<content:encoded><![CDATA[<p>kiddo; if you see lines after lines of those two things (without a poll, sleep, select, etc) in between them then you have trouble indeed.  this means that your application is running in an infinite loop and never sleeping at all (ie: is pegging the cpu at 100%).
<p />unless your app is actively doing work it shouldn&#8217;t be doing this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
