On 07/12/2018 11:08 PM, Randell Jesup wrote:
I do hope that the 100 process figures scenario that was given is a worse case
scenario though...
It's not. Worst case is a LOT worse.
Shutting down threads/threadpools when not needed or off an idle timer
is a Good thing. There may be some perf hit since it may mean starting
a thread instead of just sending a message at times; this may require
some tuning in specific cases, or leaving 1 thread or more running
anyways.
Stylo will be an interesting case here.
We may need to trade first-load time against memory use by lazy-initing
more things than now, though we did quite a bit on that already for
reducing startup time.
One thing to remember that some of the child processes will be more important than others. For example all the processes used for browsing contexts in
the foreground tab should probably prefer performance over memory (in cases that is something we can choose from), but if a process
is only used for browsing contexts in background tabs and isn't playing any
audio or such, it can probably use less memory hungry approaches.
Like, could stylo use fewer threads when used in
background-tabs-only-processes, and once the process becomes foreground, more
threads are created.
We have similar approach in many cases for performance and responsiveness
reasons, but less often for memory usage reasons.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
