77258 2012-01-27 16:00:13 -0800 run-perf-test should report memory usage 2012-01-30 17:54:18 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified NEW P2 Normal --- 77378 1 rniwa webkit-unassigned abarth cmarcelo eric kling koivisto mitz morrita tony oldest_to_newest 544473 0 rniwa 2012-01-27 16:00:13 -0800 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 544859 1 morrita 2012-01-29 20:52:12 -0800 (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. 544863 2 rniwa 2012-01-29 21:01:18 -0800 (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.