4 ms·

https://areweslimyet.com/ https://areweslimyet.com/ would indicate that a lot of the memory efficiency gains have been undone. N. Nethercote no longer writes Me

https://areweslimyet.com/ https://areweslimyet.com/ would indicate that a lot of the memory efficiency gains have been undone. N. Nethercote no longer writes MemShrink project updates and Snappy is listed under 'old projects' on mozilla wiki. Superficially, it seems like Mozilla has lost interest in the performance aspect of Firefox. I hope the opposite is actually true.

masklinn 12y ago
> N. Nethercote no longer writes MemShrink project updates Nicholas's last memshrink posts were this summer, after the FF32 release...
mccr8 12y ago
We're still working just as hard on improving the memory usage of Firefox. We have MemShrink meetings every other week. Our focus on FirefoxOS has made improving memory usage more important than ever.
nnethercote 12y ago
In the "Meeting Minutes, Progress Reports and Presentations" section of https://wiki.mozilla.org/Performance/MemShrink https://wiki.mozilla.org/Performance/MemShrink it says the following: > We no longer take meeting minutes nor make progress reports, but the meetings still happen. Brief MemShrink updates are given in the minutes of the weekly Platform meeting (wiki, blog). And nnethercote still blogs about major MemShrink occurrences. And in the post marked "The Final Progress Report" I said this: > I was due to write a MemShrink progress report today, but I’ve decided that after almost 2.5 years, my reserves of enthusiasm for these regular reports has been exhausted. Sorry! I do still plan to write posts when significant fixes relating to memory consumption are made. (For example, when generational GC lands, you’ll hear about it here.) I will also continue to periodically update the MemShrink “big ticket items” list. And MemShrink meetings will continue, so MemShrink-tagged bugs will still be triaged. And for those of you who read the weekly Platform meeting notes, I will continue to write MemShrink updates there. So don’t despair — good things will continue to happen, but they’ll just be marginally less visible. Time I don't spend writing MemShrink reports is time I can spend on improving Firefox's code.

masklinn 12y ago

> N. Nethercote no longer writes MemShrink project updates Nicholas's last memshrink posts were this summer, after the FF32 release...

mccr8 12y ago

We're still working just as hard on improving the memory usage of Firefox. We have MemShrink meetings every other week. Our focus on FirefoxOS has made improving memory usage more important than ever.

nnethercote 12y ago

In the "Meeting Minutes, Progress Reports and Presentations" section of https://wiki.mozilla.org/Performance/MemShrink https://wiki.mozilla.org/Performance/MemShrink it says the following: > We no longer take meeting minutes nor make progress reports, but the meetings still happen. Brief MemShrink updates are given in the minutes of the weekly Platform meeting (wiki, blog). And nnethercote still blogs about major MemShrink occurrences. And in the post marked "The Final Progress Report" I said this: > I was due to write a MemShrink progress report today, but I’ve decided that after almost 2.5 years, my reserves of enthusiasm for these regular reports has been exhausted. Sorry! I do still plan to write posts when significant fixes relating to memory consumption are made. (For example, when generational GC lands, you’ll hear about it here.) I will also continue to periodically update the MemShrink “big ticket items” list. And MemShrink meetings will continue, so MemShrink-tagged bugs will still be triaged. And for those of you who read the weekly Platform meeting notes, I will continue to write MemShrink updates there. So don’t despair — good things will continue to happen, but they’ll just be marginally less visible. Time I don't spend writing MemShrink reports is time I can spend on improving Firefox's code.