On Thursday, February 11, 2016 at 8:27:46 PM UTC-5, Eric Rahm wrote: > On Thursday, February 11, 2016 at 5:03:05 PM UTC-8, Patrick Meenan wrote: > > "Memory Usage" is .... complicated. Specially when you try to compare > > different architectures. > > Sure, but this is all Windows for desktop at least.
Sorry, I meant different browser architectures. Even moving from monolithic to e10s won't be directly comparable. Could be useful for comparing a single browser/architecture to itself over time though. WPT also injects itself into the parent process and adds some to the memory stats (in particular, it keeps a copy of all of the response bodies and GDI memory for screen shots) so it's not a completely clean read but should be consistent over time for a given browser. > > > Working set? Virtual memory? Accounting for shared pages, etc. > > Working set (RSS) and private working set (USS) are the most interesting > numbers. This gets tricky with multi-process setups, but a reasonable > baseline I've been looking at is |total_memory = parent_rss + sum(child_uss)| > > 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. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
