It should be pretty easy to measure at a high level with ATSY [1], but I agree coordination on overall memory requirements before adding new processes would be useful.
For more detailed breakdowns of memory usage we can depend on about:memory reports for content processes, we added support for memory reports from the GPU process recently [2], I'm not sure about the other processes; if they're just dedicated content processes then it should just work, if not they could probably piggy back off what the GPU process did. I assume WebRenderer will have it's own process, but maybe that just gets lumped in with the GPU process. -e [1] https://github.com/EricRahm/atsy [2] https://bug623317.bugzilla.mozilla.org/show_bug.cgi?id=1321492 On Mon, Mar 6, 2017 at 2:42 PM, Nicholas Nethercote <n.netherc...@gmail.com> wrote: > On Tue, Mar 7, 2017 at 9:22 AM, Ben Kelly <bke...@mozilla.com> wrote: > > > These measurements are for full content processes. Many of the processes > > in the above do not need all the chrome script we load in content > processes > > today. > > > > That's good to know. But it would still be good to get measurements of > these slimmer processes, and check that they don't contain unnecessary > stuff, and decide what coordination is necessary between the different > process types (as kmag suggested elsewhere in the thread). > > Nick > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
