On Fri, Feb 21, 2014 at 5:07 PM, Jason Duell <jduell.mcb...@gmail.com> wrote: > On 02/21/2014 01:38 PM, Nicholas Nethercote wrote: >> >> Greetings, >> >> We now live in a memory-constrained world. By "we", I mean anyone >> working on Mozilla platform code. When desktop Firefox was our only >> product, this wasn't especially true -- bad leaks and the like were a >> problem, sure, but ordinary usage wasn't much of an issue. But now >> with Firefox on Android and particularly Firefox OS, it is most >> definitely true. >> >> In particular, work is currently underway to get Firefox OS working on >> devices that only have 128 MiB of RAM. The codename for these devices >> is Tarako (https://wiki.mozilla.org/FirefoxOS/Tarako). In case it's >> not obvious, the memory situation on these devices is *tight*. >> >> Optimizations that wouldn't have been worthwhile in the desktop-only >> days are now worthwhile. For example, an optimization that saves 100 >> KiB of memory per process is pretty worthwhile for Firefox OS. > > > Thanks for the heads-up. Time to throw > > https://bugzilla.mozilla.org/show_bug.cgi?id=807359 > > back on the barbie... (Feel free to give it a new memshrink priority as you > see fit, Nicholas) > > Jason > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform
It's worth noting that data that is not written to beyond process startup will generally result in a single copy shared amongst all content processes now thanks to Nuwa. - Kyle _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
