On Tue, Mar 07, 2017 at 02:14:48PM +0200, smaug wrote:
What you mean with "chrome script"? Any chrome JS?
There is frame script overhead per tab in child processes
(around 340kB on my machine) but then we have also tons of
jsms. I see 94 chrome compartments in a child process with one
tab. And yes, that all is taking tons of memory. We really
should move more code to native.
There are other costs to moving more code to native, though.
I think there's a fair amount that we can do to reduce the
amount of JS we load into content processes. I already know some
places where we load more code than we need to, or load it too
eagerly. And there's already been some talk about moving more
code to ES6 or CommonJS modules to reduce the number of
compartments.
Those both seem like more tractable places to start than making
more code native.
Also, bfcache limits are per process, so the more we have
processes, the more we store pages in bfcache. Maybe
only-background-tabs process should evict all of its bfcache
quite soon, and not wait for up to 30mins.
It would be nice if we could try to coordinate bfcache limits
across processes. When I'm doing research, I tend to create a
lot of tabs, and switch between/navigate them a lot. I'd rather
the bfcache eviction care more about how likely I am to navigate
back to an entry than what process it's in.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
