On Friday, February 12, 2016 at 9:41:02 AM UTC-8, Patrick Meenan wrote: > > > For example with Firefox I would be interested in the RSS of the parent > > > process (firefox.exe) and the USS of the child processes > > > (plugin-container.exe). For Chrome it would be more along the lines of > > > the RSS of the main chrome process, and the USS of the > > > renderer/gpu/plugin processes (and probably the RSS of the nacl process > > > if that's still around). > > > > I can grab a one-time snapshot of these at the end of the test/page load. > > Walking the process list was too expensive to do every 100ms (which is how > > often I collect CPU utilization). Should be able to add it today and > > report both the parent RSS and sum(child_uss) as separate numbers. > > Just pushed support in WPT for collecting memory stats at the end of a test: > https://github.com/WPO-Foundation/webpagetest/commit/629f48ea5c57be57b50e1f97942c98dface593b2 > > Sample result: http://www.webpagetest.org/xmlResult/160212_3Z_12D1/ > > Specifically: > browser_process_count - Number of browser processes > browser_main_memory_kb - Full working set of the "main" browser process in KB > (main for WPT is whatever is doing the network communications) > browser_other_private_memory_kb - Sum of the private working sets for all > other browser processes (in KB) > browser_working_set_kb - Both working set numbers combined
This is great, thanks for adding it. Getting memory usage on "real" sites should be quite interesting. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
