Changes

Jump to: navigation, search

Performance/MemShrink

76 bytes added, 00:56, 15 June 2011
Additional Infrastructure
== Additional Infrastructure ==
* Automated testing using other existing tools (Valgrind, trace-malloc) should be set up.(Valgrind is covered by {{bug|631811}}.)
* jst has some ideas about using static analysis in place to automatically detect some kinds of leaks({{bug|423032}}).
* Telemetry will help a lot. There would be 2 kinds of telemetry: built-in idle-daily stats and an addon. Builtin idle-daily would report a sanitized version of about:memory, number of open tabs, among other non-privacy-invasive stats. We would also distribute a telemetry addon allowing users to opt into more invasive telemetry. This addon would be able to run benchmarks, and allow the users to explicitly trigger submission of detailed privacy/perf-invasive information (such as open websites). ({{bug|663423}})
* Mozmill endurance tests can track memory usage over time, which is much more informative than snapshot measurements or averaged measurements. It's unclear how much overhead they introduce, however. Leveraging them somehow could avoid a lot of duplicated work.
Confirm
1,345
edits

Navigation menu