From private email: Hi; If you are still using prereleass, you might want to grab the 2.7.0 release: http://gee.cs.oswego.edu/pub/misc/malloc.c I suspect that it is marginally faster in mozilla than pre6. Also, while I couldn't replicate your footprint tests (well, not without more time to collect and cache pages, etc needed to do it right), I did recheck the trace you put up. A plot of it (among others) is at http://gee.cs.oswego.edu/dl/malloc-plots/index.html -- Doug Lea
Nominating for mozilla0.9. edward, could you please try to look at this? Also, Doug may have ``fixed'' bug 73053 without forcing us to apply our own mods.
Bug 73053 is not covered by this bug or Doug's updates to 2.7.0 release. I suspect he's only tested the pthread code under Linux.
Reassigning to waterson (Chris, feel free to reassign it again).
mcafee, could you take a look at this?
The ptmalloc page <http://www.malloc.de/en/index.html> seems to imply that an older-but-more-thread-friendly adaptation of lea-malloc is used in glibc. Performancewise it could be a toss-up between the improvements added to lea-malloc since the fork and the overheads of its very coarse locking in comparison to ptmalloc/glibc. I'm certainly very interested in seeing the results!
shaver's been doing some work on this, I think.
Shaver wanna take this over ?
Yeah, I got numbers at one point but they were pretty noisy. I'll run again soon.
Untargeting from 0.9.8
glibc2.3 is taking the new ptmalloc. We should probably look at taking it too. 1.0, I say.
We're not going to take a new allocator for 1.0, and newer glibcs will soon have the sexy new ptmalloc anyway. We'll revisit this with dp when he gets back, or something.
14 years ago