Re: [whatwg] Proposal: navigator.cores

2014-05-03 Thread Eli Grey
The proposal specifically states using logical cores, which handles all of the CPUs you mentioned properly. Intel CPUs with hyperthreading enabled report logical cores as double the hardware cores. Depending on the version and configuration of the Samsung Exynos Octa big.LITTLE CPUs, you will get

Re: [whatwg] Proposal: navigator.cores

2014-05-04 Thread Eli Grey
On Sun, May 4, 2014 at 4:11 PM, Ian Hickson i...@hixie.ch wrote: or you have to examine permissions that the application is requesting, and explicitly grant it the right to run on your machine I am not aware of this in any platforms. Can you provide one example of a platform that requests an

Re: [whatwg] Proposal: navigator.cores

2014-05-05 Thread Eli Grey
We want to claim 6 in that situation. If the API claimed less than 6 on Samsung's Exynos 5 Hexa (2x A15 cores + 4x A7 cores), then the cores will be underutilized. We already experience varying performance per core with current systems (especially mobile SoCs) using uniform core hardware, simply

Re: [whatwg] Proposal: navigator.cores

2014-05-05 Thread Eli Grey
I have a list of example use cases at http://wiki.whatwg.org/wiki/NavigatorCores#Example_use_cases Each of these use cases involves a parallelizable algorithm that needs to run as fast as possible on the user's system in order for the user to have a responsive experience. You can never run any of

Re: [whatwg] Proposal: navigator.cores

2014-05-05 Thread Eli Grey
GCD exposes core count in that you can make your jobs keep track of the current time and then count how many threads are running at the same time. A GCD-style API will enable me to replace all of Core Estimator's estimation and statistical code with a very simple counter and time tracker, while

Re: [whatwg] Proposal: navigator.cores

2014-05-13 Thread Eli Grey
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