On 7/13/18 5:22 PM, gsquel...@mozilla.com wrote:
E.g., could I instrument one class, so that every allocation would be tracked automatically, and I'd get nice stats at the end?
You mean apart from just having a memory reporter for it?
Including wasted space because of larger allocation blocks?
Memory reporters using mallocSizeOf include that space, yes.
Could I even run what-if scenarios, where I could instrument a class and extract its current size but also provide an alternate size (based on what I think I could make it shrink), and in the end I'll know how much I could save overall?
You could hack the relevant memory reporter, sure.
Do we have Try tests that simulate real-world usage, so we could collect memory-usage data that's relevant to our users, but also reproducible?
See the "awsy-10s" test suite, which sort of aims to do that.
Should there be some kind of Talos-like CI tests that focus on memory usage, so we'd get some warning if a particular patch suddenly eats too much memory?
This is what awsy-e10s aims to do, yes. -Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
