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. > 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). > Optimizing for the wrong thing can have negative impacts (like optimizing for > the working set displayed in task manager is easy by forcing a process to > page out periodically but it's artificial and not good for anybody). Artificial optimizations are an unfortunate side effect of every benchmark (particularly in js-land), I'm not sure it's our place to not measure something because we think people might game it. > WebPageTest used to track it at one point but the data wasn't actually useful > so I removed it. If anyone has suggestions on how to do it in a useful way > I'd be happy to add it. See above. -e _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
