On Thu, Jul 12, 2018 at 04:08:49PM -0400, 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.
This is a really important point: Memory usage and performance deeply
intertwined.
There are hard limits on the amount of memory we can use, and the more
of it we waste needlessly, the less we have available for performance
optimizations that need it. In the worst (performance) case, we wind up
swapping, at which point performance may as well not exist.
We're going to have to make hard decisions about when/how often/how
aggressively we flush caches, spin down threads, unload tabs, ... The
more unnecessary overhead we save, the less extreme we're going to have
to be about this. And the better we get at spinning down unused threads
and evicting low impact cache entries, the less aggressive we're going
to have to be about the high impact ones. Throwing those things away
will have a performance impact, but not throwing them away will, in the
end, have a bigger one.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
