Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Trade-offs exist! How astonishing.

From https://wiki.mozilla.org/Performance/MemShrink:

"MemShrink is a project that aims to reduce Firefox's memory consumption. There are three potential benefits.

1. Speed. Firefox will be faster due to less cache pressure, less paging, and fewer/smaller GC and CC pauses. Changes that reduce memory consumption but make Firefox slower are not desirable.

2. Stability. Firefox will suffer fewer aborts/crashes due to virtual or physical memory exhaustion. The former is mostly a problem on 32-bit Windows builds with a 2GB or 4GB virtual memory limit, the latter is mostly a problem on mobile devices that lack swap space.

3. Reputation. Fewer people will complain that Firefox is a memory hog and that Mozilla ignores memory usage."



I am not a specialist on that stuff, but I note the "will". If they have launched and noticed actual improvements, I'll be interested.


nnethercote on the other hand is the "specialist" as he is in charge of the MemShrink project itself... I would trust him on this stuff.


OK, but the developers of Mozilla are specialists, too. Why not trust them? Or is nnethercote part of the Mozilla dev team? MemShrink will hopefully just be merged into the core?


I'm a Mozilla employee and started MemShrink. I also write about it regularly: http://blog.mozilla.com/nnethercote/category/memshrink/.

MemShrink has been running since June 2011 and there have been many improvements in Firefox's memory consumption since then; these have shown up in Firefox 7, 8, 9, 10 and 11.


He's part of the Mozilla dev team. Memshrink isn't a branch that's waiting to get merged, but an ongoing program to reduce overall memory usage.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: