[Webkit-unassigned] [Bug 141247] REGRESSION (bmalloc): WebKit performance tests don't report memory stats

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 13 05:06:41 PST 2015


--- Comment #3 from Csaba Osztrogon√°c <ossy at webkit.org> ---
(In reply to comment #2)
> It's not clear if we will ever get back to the precise reporting TCMalloc
> had; some of that reporting relied on expensive metadata that cause
> throughput and/or memory use problems.
> For example, TCMalloc could only do accurate reporting of committed vs
> uncommitted memory because it would synchronously over-commit huge swaths of
> memory, and synchronously commit or decommit when merging ranges, or refuse
> to merge ranges.

If it isn't possible to get back memory statistics, how can we avoid serious
memory regressions in the future? How do you measure memory consumption on OSX
since switching to bmalloc? Are you going to upstream your method to be able
run memory measurements on the performance bots again?

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150213/ce44aba7/attachment-0002.html>

More information about the webkit-unassigned mailing list