On 2014-05-13, 10:54 AM, Eli Grey wrote:
On Tue, May 13, 2014 at 1:43 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
supporting a worker pool that actually scales to how many cores you have
available
1) What is an "available core" to you? An available core to me is a
core that I can use to compute. A core under load (even 100% load) is
still a core I can use to compute.
No, you're wrong. An available core is a core which your application
can use to run computations on. If another code is already keeping it
busy with a higher priority, it's unavailable by definition.
2) Web workers were intentionally made to be memory-heavy, long-lived,
reusable interfaces. The startup and unload overhead is massive if you
actually want to dynamically resize your threadpool. Ask the people
who put Web Workers in the HTML5 spec or try benchmarking it (rapid
threadpool resizing) yourself--they are not meant to be lightweight.
How does this support your argument exactly?
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
