Changes

Jump to: navigation, search

Performance/MemShrink

192 bytes removed, 19:54, 20 November 2011
no edit summary
MemShrink is a project that aims to reduce Firefox's memory consumption. There are three potential benefits:
# Speed: . less Less cache pressure, and less paging. The latter is crucial, as it can destroy performanceand fewer/smaller GC and CC pauses.# Stability: . fewer OOMs, whether Fewer aborts/crashes due to address space physical or virtual memory exhaustion or otherwise. This results in fewer crashes (due to mishandling of OOM) or abortsThe latter is mostly a problem on 32-bit Windows builds, the former is mostly a problem on mobile.# Perception: Reputation. fewer Fewer people will complain about Firefox being a memory hog, and fewer people will complain that Mozilla ignores memory usage.
These factors are doubly important for Firefox Mobile.
There's also a [https://bugzilla.mozilla.org/show_bug.cgi?id=640791 tracking bug] for bugs relating to profiling, tools and infrastructure. (These bugs overlap several of the above lists.)
 
== Goals ==
 
The real goal is to minimize bad performance (primarily paging) caused by poor memory usage. But that's hard to track.
 
A more trackable goal is to get the number of MemShrink P1 bugs down to zero. That will mean that all the bad leaks will have been fixed, and also the important auxiliary work (e.g. infrastructure to detect regressions) will be in place.
== Current Infrastructure ==
In comparison, for AWSY there is no good and/or standard benchmark suite; metrics are less clear and/or harder to measure; the memory profiling tools aren't as good; but most importantly, there's no well-defined goal w.r.t. any benchmarks.
If we were focusing mostly on memory slimming a graph like AWFY's could work wellA more trackable goal is to get the number of MemShrink P1 bugs down to zero. But given That will mean that all the bad leaks will have been fixed, and also the primary goal above important auxiliary work (zero MemShrink P1 bugse.g. infrastructure to detect regressions)will be in place. Therefore, areweslimyet.com just points to the list of open MemShrink P1 bugs.
Confirm
1,345
edits

Navigation menu