- From: Joseph Berkovitz <joe@noteflight.com>
- Date: Fri, 25 Oct 2013 17:11:59 -0400
- To: robert@ocallahan.org
- Cc: Marcus Geelnard <mage@opera.com>, Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>, Audio WG <public-audio@w3.org>, Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, Srikumar Karaikudi Subramanian <srikumarks@gmail.com>, s p <sebpiq@gmail.com>
> Another thing is that it doesn't really make sense to create 1 worker per node. You'd be much better off using a single worker for all nodes on a given page, or at most one worker per CPU core the system has. I agree, although I also think this remark of ROC's also highlights the fact that "Worker" has slightly different meanings for different people. On the one hand, "Worker" represents the abstract idea of "a designated script running in a controlled, isolated runtime environment". I think that is the way many of us are talking about it. On the other hand, it also represents a pre-existing implementation concept that has various known costs and overheads. ..Joe
Received on Friday, 25 October 2013 21:12:27 UTC