<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Warning. This one is a little bit technical</title>
	<link>http://pvanhoof.be/blog/index.php/2008/01/04/warning-this-one-is-a-little-bit-technical</link>
	<description>From the mind of Philip</description>
	<pubDate>Sun, 14 Mar 2010 03:54:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Justin Dolske</title>
		<link>http://pvanhoof.be/blog/index.php/2008/01/04/warning-this-one-is-a-little-bit-technical#comment-16747</link>
		<pubDate>Fri, 04 Jan 2008 02:27:07 +0000</pubDate>
		<guid>http://pvanhoof.be/blog/index.php/2008/01/04/warning-this-one-is-a-little-bit-technical#comment-16747</guid>
					<description>You might check out some of the work Mozilla has been doing to optimize Firefox's memory usage... See http://blog.pavlov.net/

One area a lot of work has gone into is reducing heap fragmentation. [Sounds like you might be alluding to this in the paragraph before &quot;Average Joe Six Pack&quot;?] The basic symptom of the problem is finding that VM usage can significantly exceed the actual number of bytes that are allocated -- you might not have much memory allocated, but because of the way that memory is distributed across pages it pulls in a lot more with it.

Changing the way memory is used (eg, switching to stack allocations, using arenas, avoiding small ephemeral allocations, altering allocation patterns, etc) helps avoid fragmentation, and thus overall memory consumption/paging.</description>
		<content:encoded><![CDATA[<p>You might check out some of the work Mozilla has been doing to optimize Firefox&#8217;s memory usage&#8230; See <a href='http://blog.pavlov.net/' rel='nofollow'>http://blog.pavlov.net/</a></p>
<p>One area a lot of work has gone into is reducing heap fragmentation. [Sounds like you might be alluding to this in the paragraph before &#8220;Average Joe Six Pack&#8221;?] The basic symptom of the problem is finding that VM usage can significantly exceed the actual number of bytes that are allocated &#8212; you might not have much memory allocated, but because of the way that memory is distributed across pages it pulls in a lot more with it.</p>
<p>Changing the way memory is used (eg, switching to stack allocations, using arenas, avoiding small ephemeral allocations, altering allocation patterns, etc) helps avoid fragmentation, and thus overall memory consumption/paging.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
