2008/6/24 Roland Mainz <roland.mainz at nrubsig.org>: > Technically there was an discussion on the last OpenSolaris.org summit > to check whether it may sense to replace libc's malloc implementation > with the libast one since it's faster, works better with small > allocations, scales better up to very large memory allocations, avoids > fragmentation for long-running application (something which hit > FireFox+Mozilla/Seamonkey and other applications _badly_), has builtin > libumem-like memory checking functionality and is async-signal safe (not > the one currently in OS/Net, that was a new development for the one > which the ksh93-integration update1 will deliver). The only problem so > far was that I didn't had time to take a look yet... ;-(
How does libast's malloc compared to jemalloc that Firefox 3 uses on Windows? -- Shawn Walker
