[webkit-dev] support for navigator.cores or navigator.hardwareConcurrency
oliver at apple.com
Mon May 5 18:23:54 PDT 2014
On May 5, 2014, at 6:13 PM, Rik Cabanier <cabanier at gmail.com> wrote:
> Do you really want a page to know that you have a fancy-pants 24-core Mac Pro rather than a little Mac mini?
> If I have 24 cores ready to do work and the page can put them to use, I would like it to do so.
> At the same time, if I just have a old mac mini, I don't want the page to launch 24 workers as that will exhaust my memory and cause contention.
But I don't have 24 cores available, i have 24 cores installed. You have no idea what the actual workload of the system is, you don't know whether any other tabs are also using workers, you only have one piece of information, and that is nowhere near sufficient to make a reasonable choice.
A better solution would be to have a WorkerSet API where the browser is able to make a sensible choice given the current system, system load, power source, etc, etc
Generating workloads on the basis of # of installed cores has be attempted on every environment and it almost always leads to incorrect choices being made.
> On May 5, 2014, at 4:58 PM, Filip Pizlo <fpizlo at apple.com> wrote:
>> I like this. Personally, I don't see any downside.
>> Is there a bug (on bugs.webkit.org), and if not, can you create one? :-)
>> On May 5, 2014 at 4:49:35 PM, Rik Cabanier (cabanier at gmail.com) wrote:
>>> there's a thread on blink-dev  and whatwg  to create a new parameter on the navigator object that returns the maximum number of tasks that can run in parallel. 
>>> Is this something that WebKit would support?
>>> 1: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/B6pQClqfCp4
>>> 2: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2014-May/254200.html
>>> 3: http://wiki.whatwg.org/wiki/NavigatorCores
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev