[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 09:30:01 PST 2015


Sam Weinig <sam at webkit.org> changed:

           What    |Removed                     |Added
                 CC|                            |sam at webkit.org

--- Comment #6 from Sam Weinig <sam at webkit.org> ---
(In reply to comment #3)
> (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
> since switching to bmalloc? Are you going to upstream your method to be able
> run memory measurements on the performance bots again?

We have never really relied on malloc statistics for our memory testing.  On OS X we use the `footprint` tool, though in the past, we have used tools like `heap` and `vmmap`.  These tools give better indications of memory use, as they include all of the allocators on the system.

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/5dfa37f4/attachment-0002.html>

More information about the webkit-unassigned mailing list