On Tue, May 5, 2015 at 12:42 AM, Nicholas Nethercote <n.netherc...@gmail.com> wrote: > On Mon, May 4, 2015 at 11:53 PM, Leman Bennett (Omega X) > <Redacted.For.Spam@request.contact> wrote: >> >> I heard that there was rumor of a plan to limit process count spawn to >> per-domain. But I've not seen offhand of a bug filed for it or anything else >> that relates to achieving more than one content process instance. > > There are multiple competing factors when it comes to choosing the > right number of processes. > > - For security, more processes is better; one per tab is probably ideal. > > - For crash protection, ditto. > > - For responsiveness, one process per CPU core is probably best. > > - For memory usage, one process is probably best.
Actually, what you generally want to do is to switch process when the user navigates from one "website" to another in a given tab. And then kill off the old process. One big benefit that this provides is that it cleans up any memory leaks. So there are memory advantages to this approach. Another approach is that we should eventually move to a process-per-origin model, where we can actually use the sandbox to ensure that different websites can't steal each other's data, even if we have a buffer overflow somewhere in gecko. / Jonas _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
