zoltan at webkit.org
Mon Sep 30 19:41:45 PDT 2013
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.
On Mon, Sep 30, 2013 at 2:48 PM, Geoffrey Garen <ggaren at 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?
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev