- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Jul 2013 22:40:00 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22723 --- Comment #12 from Srikumar Subramanian (Kumar) <srikumarks@gmail.com> --- (In reply to comment #11) > The 4ms delay is probably with relation to setTimeout(), right? That is > enforeced artificially by browsers in order to prevent web pages from > spamming the main thread in exactly this way, it is not the actual delay of > event delivery. In reality, the event delivery delays really depend on a > lot of factors invisible to the web application, such as how busy the event > loop is. But it should be *much* lower than 4ms under most circumstances. Not entirely. With the realtime script processor nodes, I've needed a buffer size of at least 1024 to avoid glitches due to UI events. Since that amounts to 23ms, I thought I was being rather optimistic in picking 4ms :) -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 19 July 2013 22:40:01 UTC