Hi Geoffrey, I used to work on memory related topics, while I was working on the University of Szeged.
Based on a 2.5-year-old measurement ( http://webkit.sed.hu/blog/20100302/war-allocators-qtlaunchers-coast) on the Qt-port, the page loading on the Methanol test suite was 5% faster (avg) with TCmalloc than the default system allocator on Linux. The performance results of the SunSpider suite was similar for both allocators. The memory consumption was always lower with the default os allocator. I guess the new allocator only has iOS support. I'm fine with removing TCmalloc, although this direction might raises further questions, like removing the custom allocation framework also. Feel free to cc me on bugs, I can help by contributing some patches. Cheers, <Zoltan> On Mon, Sep 30, 2013 at 2:48 PM, Geoffrey Garen <gga...@apple.com> wrote: > Hi folks. > > I’m planning to remove our years-out-of-date port of TCMalloc, and replace > it with something that takes maximum advantage of Mac and iOS virtual > memory, threading, and security APIs. > > I've heard that TCMalloc has caused some problems for non-Mac, non-iOS > ports in the past. So, if you maintain a port, this change might make > things simpler for you. > > Are there any ports whose built-in malloc implementations are slow enough > that they can’t get by without TCMalloc? > > Thanks, > Geoff > _______________________________________________ > webkit-dev mailing list > firstname.lastname@example.org > https://lists.webkit.org/mailman/listinfo/webkit-dev >
_______________________________________________ webkit-dev mailing list email@example.com https://lists.webkit.org/mailman/listinfo/webkit-dev