- From: Olivier Thereaux <notifications@github.com>
- Date: Wed, 11 Sep 2013 07:29:43 -0700
- To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Received on Wednesday, 11 September 2013 14:30:28 UTC
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#8) by Philip Jägenstedt on W3C Bugzilla. Wed, 13 Jun 2012 10:16:37 GMT 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. --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/issues/113#issuecomment-24244340
Received on Wednesday, 11 September 2013 14:30:28 UTC