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. I'd be loathe to use as many processes as Chrome does, which is something like one per domain (AIUI). I've heard countless times that Chrome basically falls over once you get past 60 or 70 tabs, and I've always assumed that this is due to memory usage, or possibly some kind of IPC scaling issue. In contrast, plenty of Firefox users have 100+ tabs, and there are some that even have 1000+. I think it's crucial that we continue working well for such users. With all that in mind, my hope/guess is that we'll end up one day with one process per CPU core, because it's the middle ground. Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
