<?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: Studying Fennec Performance</title>
	<atom:link href="http://blog.mozilla.com/tglek/2009/06/26/studying-fennec-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/tglek/2009/06/26/studying-fennec-performance/</link>
	<description>Just another Blog.mozilla.com weblog</description>
	<lastBuildDate>Sun, 12 Feb 2012 07:38:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Eero Tamminen</title>
		<link>http://blog.mozilla.com/tglek/2009/06/26/studying-fennec-performance/comment-page-1/#comment-30832</link>
		<dc:creator>Eero Tamminen</dc:creator>
		<pubDate>Sat, 16 Apr 2011 09:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/tglek/?p=140#comment-30832</guid>
		<description>&gt; Linux is a crappy platform in this case because it’s running on ARM where oprofile barely does anything and there are no other performance tools for N810

Best thing in optimizing code is understanding what it does.  Oprofile can provide whole system bottleneck functions.  However, trying to take callgraphs on a slow system like N810 is not really that useful or much fun, so I typically use valgrind / callgrind / kcachegrind on desktop for analyzing how a particular process&#039; code arrives at/uses the bottleneck functions that Oprofile highlighted.

As long as the code logic is same on two platforms, this works really fine.

Strace and functracer give also interesting information although they don&#039;t directly tell about the performance:
http://stage.maemo.org/pool/diablo/free/s/strace/
http://stage.maemo.org/pool/diablo/free/f/functracer/</description>
		<content:encoded><![CDATA[<p>&gt; Linux is a crappy platform in this case because it’s running on ARM where oprofile barely does anything and there are no other performance tools for N810</p>
<p>Best thing in optimizing code is understanding what it does.  Oprofile can provide whole system bottleneck functions.  However, trying to take callgraphs on a slow system like N810 is not really that useful or much fun, so I typically use valgrind / callgrind / kcachegrind on desktop for analyzing how a particular process&#8217; code arrives at/uses the bottleneck functions that Oprofile highlighted.</p>
<p>As long as the code logic is same on two platforms, this works really fine.</p>
<p>Strace and functracer give also interesting information although they don&#8217;t directly tell about the performance:<br />
<a href="http://stage.maemo.org/pool/diablo/free/s/strace/" rel="nofollow">http://stage.maemo.org/pool/diablo/free/s/strace/</a><br />
<a href="http://stage.maemo.org/pool/diablo/free/f/functracer/" rel="nofollow">http://stage.maemo.org/pool/diablo/free/f/functracer/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeetendra</title>
		<link>http://blog.mozilla.com/tglek/2009/06/26/studying-fennec-performance/comment-page-1/#comment-23454</link>
		<dc:creator>Jeetendra</dc:creator>
		<pubDate>Fri, 18 Sep 2009 10:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/tglek/?p=140#comment-23454</guid>
		<description>Hi Tara,

I wont to measure the time needed to load a site (Page).
Can u help me out?</description>
		<content:encoded><![CDATA[<p>Hi Tara,</p>
<p>I wont to measure the time needed to load a site (Page).<br />
Can u help me out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curtis Bartley</title>
		<link>http://blog.mozilla.com/tglek/2009/06/26/studying-fennec-performance/comment-page-1/#comment-22771</link>
		<dc:creator>Curtis Bartley</dc:creator>
		<pubDate>Sat, 27 Jun 2009 17:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/tglek/?p=140#comment-22771</guid>
		<description>I&#039;ve been using source-level instrumentation to get callgraphs out of Firefox.  This approach is deficient in all sorts of ways but it does save you the trouble of looking up symbols.  For me the real problem is not getting decent data, it&#039;s simply being able to visualize the data that I can collect.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using source-level instrumentation to get callgraphs out of Firefox.  This approach is deficient in all sorts of ways but it does save you the trouble of looking up symbols.  For me the real problem is not getting decent data, it&#8217;s simply being able to visualize the data that I can collect.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

