W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Wed, 13 Jun 2012 10:16:38 +0000
To: public-audio@w3.org
Message-Id: <E1Sekcw-0004uu-1V@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #9 from Philip J <philipj@opera.com> 2012-06-13 10:16:37 UTC ---
To get an idea of how long a layout reflow can take, visit
http://www.whatwg.org/specs/web-apps/current-work/ wait for it to load and then
run javascript:alert(opera.reflowCount + ' reflows in ' + opera.reflowTime + '
ms')

On my very fast developer machine, the results are:

22 reflows in 19165.749624967575 ms

That means that in the best case (all reflows took the same amount of time) the
longest reflow was 871 ms.

With https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html I
got these results:

7 reflows in 79.2522840499878 ms

Unfortunately the longest reflow isn't exposed, but even if it's "only" 12 ms
that means that it's not hard to go way beyond that on a slower machine, like a
smartphone.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 13 June 2012 10:16:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 June 2012 10:16:40 GMT