<?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: analyzing linker max vsize</title>
	<atom:link href="http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/</link>
	<description>Improving performance at Mozilla</description>
	<lastBuildDate>Sat, 20 Apr 2013 10:00:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Nathan Froyd</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-801</link>
		<dc:creator>Nathan Froyd</dc:creator>
		<pubDate>Tue, 22 Jan 2013 21:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-801</guid>
		<description><![CDATA[Is the non-presence of a webrtc merge in pushlog merely an instance of pushlog brokenness, then?  I see the strip commits, which I remember from the webrtc landing, but I don&#039;t see anything associated with the landing itself.]]></description>
		<content:encoded><![CDATA[<p>Is the non-presence of a webrtc merge in pushlog merely an instance of pushlog brokenness, then?  I see the strip commits, which I remember from the webrtc landing, but I don&#8217;t see anything associated with the landing itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randell Jesup</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-800</link>
		<dc:creator>Randell Jesup</dc:creator>
		<pubDate>Tue, 22 Jan 2013 21:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-800</guid>
		<description><![CDATA[The early October jump was the remainder of webrtc landing in m-c from alder (signaling in particular (&gt;200Klines), also mtransport, datachannels I think and other pieces)]]></description>
		<content:encoded><![CDATA[<p>The early October jump was the remainder of webrtc landing in m-c from alder (signaling in particular (&gt;200Klines), also mtransport, datachannels I think and other pieces)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guilherme Lima</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-799</link>
		<dc:creator>Guilherme Lima</dc:creator>
		<pubDate>Tue, 22 Jan 2013 20:59:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-799</guid>
		<description><![CDATA[The topics on Mozillazine with theses days are:
http://forums.mozillazine.org/viewtopic.php?f=23&amp;t=2564537 (10-05)
http://forums.mozillazine.org/viewtopic.php?f=23&amp;t=2565929 (10-06)
http://forums.mozillazine.org/viewtopic.php?f=23&amp;t=2566595 (10-07)
http://forums.mozillazine.org/viewtopic.php?f=23&amp;t=2567657 (10-08)
Maybe the name of the bugs can help to find those that added a lot of code?]]></description>
		<content:encoded><![CDATA[<p>The topics on Mozillazine with theses days are:<br />
<a href="http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2564537" rel="nofollow">http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2564537</a> (10-05)<br />
<a href="http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2565929" rel="nofollow">http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2565929</a> (10-06)<br />
<a href="http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2566595" rel="nofollow">http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2566595</a> (10-07)<br />
<a href="http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2567657" rel="nofollow">http://forums.mozillazine.org/viewtopic.php?f=23&#038;t=2567657</a> (10-08)<br />
Maybe the name of the bugs can help to find those that added a lot of code?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Froyd</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-798</link>
		<dc:creator>Nathan Froyd</dc:creator>
		<pubDate>Tue, 22 Jan 2013 20:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-798</guid>
		<description><![CDATA[You could bisect it, sure.  It&#039;d take a couple of days to do so, though.]]></description>
		<content:encoded><![CDATA[<p>You could bisect it, sure.  It&#8217;d take a couple of days to do so, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-797</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Tue, 22 Jan 2013 20:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-797</guid>
		<description><![CDATA[&gt; There’s nothing in any of them that jumps out.
Wouldn&#039;t this be something for a bisect?]]></description>
		<content:encoded><![CDATA[<p>&gt; There’s nothing in any of them that jumps out.<br />
Wouldn&#8217;t this be something for a bisect?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Froyd</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-796</link>
		<dc:creator>Nathan Froyd</dc:creator>
		<pubDate>Tue, 22 Jan 2013 19:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-796</guid>
		<description><![CDATA[It&#039;s faster to have as much stuff as you can packed into a single library; inter-library calls are relatively more expensive than intra-library calls.  I think there might also be some disk I/O wins from having all the code in a single file (don&#039;t have to seek around the disk to get to multiple files at startup).

Your suggestion has been done in the past to get the linker&#039;s required memory down to something manageable.  We can now turn on aggressive optimizations on a per-directory basis in the source tree, and that&#039;s somewhat easier than moving things out of libxul.  There may come another point where we have to move code out of libxul again, though.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s faster to have as much stuff as you can packed into a single library; inter-library calls are relatively more expensive than intra-library calls.  I think there might also be some disk I/O wins from having all the code in a single file (don&#8217;t have to seek around the disk to get to multiple files at startup).</p>
<p>Your suggestion has been done in the past to get the linker&#8217;s required memory down to something manageable.  We can now turn on aggressive optimizations on a per-directory basis in the source tree, and that&#8217;s somewhat easier than moving things out of libxul.  There may come another point where we have to move code out of libxul again, though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ferongr</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-795</link>
		<dc:creator>ferongr</dc:creator>
		<pubDate>Tue, 22 Jan 2013 19:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-795</guid>
		<description><![CDATA[What&#039;s the rationale for not splitting the catch-all XUL.dll into multiple libraries (since linking xul.dll is what causes the linker to run out of address space AIU)?]]></description>
		<content:encoded><![CDATA[<p>What&#8217;s the rationale for not splitting the catch-all XUL.dll into multiple libraries (since linking xul.dll is what causes the linker to run out of address space AIU)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Froyd</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-794</link>
		<dc:creator>Nathan Froyd</dc:creator>
		<pubDate>Tue, 22 Jan 2013 18:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-794</guid>
		<description><![CDATA[The drop in June corresponds to http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=95d1bb200f4e15f340abb59a883713a2edc55861&amp;tochange=dc410944aabcab8ff2825d7e8d3f3391e3fe5876

Which is not very helpful, because nothing jumps out as shouting that &quot;I made vsize go down by 200MB!&quot;]]></description>
		<content:encoded><![CDATA[<p>The drop in June corresponds to <a href="http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=95d1bb200f4e15f340abb59a883713a2edc55861&#038;tochange=dc410944aabcab8ff2825d7e8d3f3391e3fe5876" rel="nofollow">http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=95d1bb200f4e15f340abb59a883713a2edc55861&#038;tochange=dc410944aabcab8ff2825d7e8d3f3391e3fe5876</a></p>
<p>Which is not very helpful, because nothing jumps out as shouting that &#8220;I made vsize go down by 200MB!&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: glandium</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-793</link>
		<dc:creator>glandium</dc:creator>
		<pubDate>Tue, 22 Jan 2013 18:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-793</guid>
		<description><![CDATA[I wouldn&#039;t be surprised if http://hg.mozilla.org/mozilla-central/rev/ae0b2ba1e47e participates greatly in the 2012-05-18 increase.]]></description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t be surprised if <a href="http://hg.mozilla.org/mozilla-central/rev/ae0b2ba1e47e" rel="nofollow">http://hg.mozilla.org/mozilla-central/rev/ae0b2ba1e47e</a> participates greatly in the 2012-05-18 increase.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: glandium</title>
		<link>http://blog.mozilla.org/nfroyd/2013/01/22/analyzing-linker-max-vsize/#comment-792</link>
		<dc:creator>glandium</dc:creator>
		<pubDate>Tue, 22 Jan 2013 18:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.org/nfroyd/?p=120#comment-792</guid>
		<description><![CDATA[What&#039;s interesting is the drop in June.]]></description>
		<content:encoded><![CDATA[<p>What&#8217;s interesting is the drop in June.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
