Changes

Jump to: navigation, search

Performance/MemShrink

11 bytes removed, 05:21, 10 March 2011
An alternative approach
== Other Ideas ==
=== An alternative approach User Reports ===
Good metrics are more difficult for memory usage than they are for cpu time. Mostly this is bad, but we may be able to use it to our advantage because it means it's harder for people to show that Firefox is using more memory than another browser. i.e. you can't load up the equivalent to sunspider in both browsers and immediately see which is better. This means that impact of bad memory usage is based on experience during regular browsing.
I wonder if we could add something to Firefox input like "Report Firefox using too much memory" we could then upload the contents of about:memory. This can help us get a better picture of when our users have the perception that we're using too much memory. It also gives us a better opportunity to discover memory leaks that are happening in the field.
Confirm
1,345
edits

Navigation menu