On Fri, Feb 21, 2014 at 5:28 PM, Till Schneidereit <t...@tillschneidereit.net> wrote: > Does that mean that bug 964057[1] will automatically cause all self-hosting > state to be shared amongst content processes, too? > > [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=964057 > > > On Sat, Feb 22, 2014 at 2:12 PM, Kyle Huey <m...@kylehuey.com> wrote: >> >> 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 > >
If your data is read-only after the point at which Nuwa forks the process (which is once things are mostly loaded but before we load the app) then generally yes. It's copy-on-write at page granularity of course, so if you have sub-page allocations you can't guarantee that it won't be copied. - Kyle _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
