On Tue, May 13, 2014 at 1:15 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
> this proposal seems to assume that the UA itself is using a very
> few cores

The proposal does not assume anything regarding current system load.
If the UA is using every core for some CPU-intensive operation, then
navigator.hardwareConcurrency should still be exactly the same value.
It represents maximum concurrency potential available, not currently
unused concurrency.

Once the UA is done with whatever CPU-intensive operations it needs to
do, then threadpools previously sized with
navigator.hardwareConcurrency will return to nominal performance. Let
the OS scheduler do what it does best.

Reply via email to