Bug 77258 - run-perf-test should report memory usage
Summary: run-perf-test should report memory usage
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 77378
  Show dependency treegraph
 
Reported: 2012-01-27 16:00 PST by Ryosuke Niwa
Modified: 2012-01-30 17:54 PST (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2012-01-27 16:00:13 PST
Right now, performance tests can only measure run-time performance. We should provide a way to measure memory usage as well.

For example, Chromium pert bots report various peak/average memory usage: http://build.chromium.org/f/chromium/perf/xp-release-dual-core/dom_perf/report.html?history=150&rev=-1&graph=vm_peak_b
Comment 1 Hajime Morrita 2012-01-29 20:52:12 PST
(In reply to comment #0)
> Right now, performance tests can only measure run-time performance. We should provide a way to measure memory usage as well.
> 
> For example, Chromium pert bots report various peak/average memory usage: http://build.chromium.org/f/chromium/perf/xp-release-dual-core/dom_perf/report.html?history=150&rev=-1&graph=vm_peak_b
Interesting. I think not all tests need this.
But having HTML5 standard in our portfolio for this purpose will help recent memory hunting effort.
Comment 2 Ryosuke Niwa 2012-01-29 21:01:18 PST
(In reply to comment #1)
> Interesting. I think not all tests need this.
> But having HTML5 standard in our portfolio for this purpose will help recent memory hunting effort.

There are many other pages with interesting characteristics (e.g. lots of javascirpt, lots of text, lots of bidi-text, etc...) we may want to keep track of. The most important question is which value we measure/report.