Comments on: Memory fragmentation http://blog.pavlov.net/2007/11/10/memory-fragmentation/ Ramblings from the mind of Stuart Parmenter Sat, 19 Jul 2008 11:12:50 +0000 http://wordpress.org/?v=MU By: Il consumo di memoria di Firefox 3 » Macpod.it http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-3247 Il consumo di memoria di Firefox 3 » Macpod.it Tue, 25 Mar 2008 10:44:07 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-3247 [...] esecuzione per lungo tempo possono facilmente arrivare a sprecare molta memoria a causa della sua frammentazione: dovendo utilizzare molte allocazioni di differenti dimensioni possono rimanere una quantità di [...] [...] esecuzione per lungo tempo possono facilmente arrivare a sprecare molta memoria a causa della sua frammentazione: dovendo utilizzare molte allocazioni di differenti dimensioni possono rimanere una quantità di [...]

]]> By: Firefox 3 Memory Usage « pavlov.net http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-2885 Firefox 3 Memory Usage « pavlov.net Wed, 12 Mar 2008 06:18:58 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-2885 [...] about before, long running applications such as ours can wind up wasting a lot of space due to memory fragmentation. This can occur as a result of mixing lots of various sized allocations and can leave a lot of [...] [...] about before, long running applications such as ours can wind up wasting a lot of space due to memory fragmentation. This can occur as a result of mixing lots of various sized allocations and can leave a lot of [...]

]]> By: Sergey Solyanik http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-2851 Sergey Solyanik Tue, 19 Feb 2008 22:52:27 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-2851 Standard ways of dealing with fragmentation are fixed memory allocators and arenas. Both map naturally into browser's workflow. See here: http://1-800-magic.blogspot.com/2007/11/guerilla-guide-to-native-memory.html Standard ways of dealing with fragmentation are fixed memory allocators and arenas. Both map naturally into browser’s workflow. See here:

http://1-800-magic.blogspot.com/2007/11/guerilla-guide-to-native-memory.html

]]> By: Firefox 3 Beta 2 released « Dataland http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-1773 Firefox 3 Beta 2 released « Dataland Thu, 20 Dec 2007 19:53:42 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-1773 [...] For a technical perspective on Firefox memory leaks (and memory usage), be sure to check out Pavlov, a Firefox developer. [...] [...] For a technical perspective on Firefox memory leaks (and memory usage), be sure to check out Pavlov, a Firefox developer. [...]

]]> By: Sandro Magi http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-1761 Sandro Magi Thu, 20 Dec 2007 16:12:56 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-1761 Two papers analyzing memory allocation that are of interest: Reconsidering Custom Memory Allocation http://www.cs.umass.edu/%7Eemery/pubs/berger-oopsla2002.pdf Scalable Locality-Conscious Multithreaded Memory Allocation http://people.cs.vt.edu/~scschnei/papers/ismm06.pdf They both propose generalizations of heaps and arenas. Two papers analyzing memory allocation that are of interest:

Reconsidering Custom Memory Allocation
http://www.cs.umass.edu/%7Eemery/pubs/berger-oopsla2002.pdf

Scalable Locality-Conscious Multithreaded Memory Allocation
http://people.cs.vt.edu/~scschnei/papers/ismm06.pdf

They both propose generalizations of heaps and arenas.

]]> By: Chris http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-1760 Chris Thu, 20 Dec 2007 15:45:45 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-1760 "As as last resort, we could replace malloc and new entirely with something more generally better." As Julien C said, I don't see why you think this a last resort. Because it would require changes throughout the codebase? That's true, but I think the first step should be to have a single unified memory manager, even if right now all it does is call malloc and free. It would give you a lot of flexibility for monitoring and customizing your memory management. “As as last resort, we could replace malloc and new entirely with something more generally better.”

As Julien C said, I don’t see why you think this a last resort. Because it would require changes throughout the codebase? That’s true, but I think the first step should be to have a single unified memory manager, even if right now all it does is call malloc and free. It would give you a lot of flexibility for monitoring and customizing your memory management.

]]> By: Scurz’s blog » Les fuites de memoire avec Iceweasel (= Firefox) http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-1564 Scurz’s blog » Les fuites de memoire avec Iceweasel (= Firefox) Mon, 17 Dec 2007 20:30:48 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-1564 [...] premier article explique un peu le problème via des exemples (images) et explique bien le réel problème [...] [...] premier article explique un peu le problème via des exemples (images) et explique bien le réel problème [...]

]]> By: Things n’ Stuff » Blog Archive » More on Firefox and some on memory leaks http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-1115 Things n’ Stuff » Blog Archive » More on Firefox and some on memory leaks Sun, 09 Dec 2007 14:51:05 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-1115 [...] Stuart Parmenter investigated this issue and his results are that this is all about memory fragmentation. As the blog post that I read that references this claims - Firefox doesn’t use a lot of memory, it just looks like it. This is of course a gross underestimation of the problem, because it doesn’t matter what the user perceives as high memory usage, but what the operating system perceives as high memory usage and as Stewart Parmenter’s results show - the operating system sees Firefox gobbling lots of memory and doesn’t care that the browser doesn’t use most of it. [...] [...] Stuart Parmenter investigated this issue and his results are that this is all about memory fragmentation. As the blog post that I read that references this claims - Firefox doesn’t use a lot of memory, it just looks like it. This is of course a gross underestimation of the problem, because it doesn’t matter what the user perceives as high memory usage, but what the operating system perceives as high memory usage and as Stewart Parmenter’s results show - the operating system sees Firefox gobbling lots of memory and doesn’t care that the browser doesn’t use most of it. [...]

]]> By:   Firefox 2 mit neuer Betaphase… by + mzungu’s weblog + http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-860   Firefox 2 mit neuer Betaphase… by + mzungu’s weblog + Sat, 01 Dec 2007 02:11:04 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-860 [...] mit dem leidigen Problem des steigenden Speicherverbrauchs (Memory Leaks) von Firefox auseinander (hier ein Blogpost dazu). Ein kurzer Blick in meinen Task-Manager: 202MB im Arbeitsspeicher nach dem Firefox-Neustart von [...] [...] mit dem leidigen Problem des steigenden Speicherverbrauchs (Memory Leaks) von Firefox auseinander (hier ein Blogpost dazu). Ein kurzer Blick in meinen Task-Manager: 202MB im Arbeitsspeicher nach dem Firefox-Neustart von [...]

]]> By: kuidas ilma flopidraivita buuditav CD teha at fruktlog http://blog.pavlov.net/2007/11/10/memory-fragmentation/#comment-854 kuidas ilma flopidraivita buuditav CD teha at fruktlog Fri, 30 Nov 2007 16:14:57 +0000 http://pavlovdotnet.wordpress.com/2007/11/10/memory-fragmentation/#comment-854 [...] beetasid, mis tõotavad palju uut ja ägedat (ja lõpuks ometi tegelevad nad tõsiselt jõudluse ja mälu probleemidega). Aga sellest kõigest ei viitsi praegu kirjutada, civ4 tahab [...] [...] beetasid, mis tõotavad palju uut ja ägedat (ja lõpuks ometi tegelevad nad tõsiselt jõudluse ja mälu probleemidega). Aga sellest kõigest ei viitsi praegu kirjutada, civ4 tahab [...]

]]>