> > Do you think it would be feasible that the browser fires events every time
> > the number of cores available for a job changes? That might allow to build
> > an efficient event-based worker pool.
>
> I think this will be very noisy and might cause a lot of confusion.
> Also I'm unsure how we c
Here's the naive worker pool implementation I was thinking about. It requires
that the browser fires an event everytime a core becomes available (only in an
active tab of course), and provide a property that tells whether or not a core
is available at a given time:
// a handler that runs when a
Do you think it would be feasible that the browser fires events every time the
number of cores available for a job changes? That might allow to build an
efficient event-based worker pool.
In the meantime, there are developers out there who are downloading
micro-benchmarks on every client to str
3 matches
Mail list logo
