W3C home > Mailing lists > Public > public-audio@w3.org > January to March 2012

Re: oscillators and the Web Audio API

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 9 Feb 2012 10:50:12 +1300
Message-ID: <CAOp6jLYUjfMrfm-TxociU0UXCcimPdp0AZcyjxT76d7RWcL98A@mail.gmail.com>
To: Chris Rogers <crogers@google.com>
Cc: public-audio@w3.org
On Thu, Feb 9, 2012 at 10:32 AM, Chris Rogers <crogers@google.com> wrote:

> On Wed, Feb 8, 2012 at 1:28 PM, Robert O'Callahan <robert@ocallahan.org>wrote:
>
>> No. Workers use a thread pool.
>>
>
> And how many actual threads would be created on say a quad-core or 8-core
> machine?
>

I don't know off the top of my head, it's all handled by the existing
Workers implementation.


> How are you managing synchronization between the different threads to
> minimize latency and avoid glitches given the kernel scheduling latency?
>  Are these threads high-priority?
>

Latency feels OK in my demos, but I haven't done anything to measure and
minimize it yet.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not
in us. If we confess our sins, he is faithful and just and will forgive us
our sins and purify us from all unrighteousness. If we claim we have not
sinned, we make him out to be a liar and his word is not in us." [1 John
1:8-10]
Received on Wednesday, 8 February 2012 21:50:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 8 February 2012 21:50:47 GMT