Re: [MMUSIC] Information on timer accuracy in browsers
Harald Alvestrand <harald@alvestrand.no> Fri, 24 July 2015 07:49 UTC
Return-Path: <harald@alvestrand.no>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7781F1B2FF5 for <mmusic@ietfa.amsl.com>; Fri, 24 Jul 2015 00:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UZw2fmQ_S2-f for <mmusic@ietfa.amsl.com>; Fri, 24 Jul 2015 00:49:50 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7201B3007 for <mmusic@ietf.org>; Fri, 24 Jul 2015 00:49:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 305137C0CFF for <mmusic@ietf.org>; Fri, 24 Jul 2015 09:49:43 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PTP8iYUAXlG8 for <mmusic@ietf.org>; Fri, 24 Jul 2015 09:49:42 +0200 (CEST)
Received: from [IPv6:2001:67c:370:176:c5a7:9419:2feb:bfa3] (unknown [IPv6:2001:67c:370:176:c5a7:9419:2feb:bfa3]) by mork.alvestrand.no (Postfix) with ESMTPSA id DD6707C0177 for <mmusic@ietf.org>; Fri, 24 Jul 2015 09:49:41 +0200 (CEST)
Message-ID: <55B1EE14.4020108@alvestrand.no>
Date: Fri, 24 Jul 2015 09:49:40 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <CABkgnnW=WRX7xRbNFRDprGOeM+Q8Yfj82pg+KfwhFfptOxbeag@mail.gmail.com>
In-Reply-To: <CABkgnnW=WRX7xRbNFRDprGOeM+Q8Yfj82pg+KfwhFfptOxbeag@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/FWcmi-DUQ14-IG8Q1RyxOzJhQ8I>
Subject: Re: [MMUSIC] Information on timer accuracy in browsers
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jul 2015 07:49:52 -0000
On 07/24/2015 09:39 AM, Martin Thomson wrote: > http://www.dslreports.com/shownews/Javascript-setInterval-accuracy-per-browser-133594 > > _______________________________________________ > mmusic mailing list > mmusic@ietf.org > https://www.ietf.org/mailman/listinfo/mmusic This shows (I think) averages. Is there a distribution? (I'd be less worried about a predictable 15-20 ms late than about an average of 5 ms with occasional spikes to 2000 ms. The single-threaded JS model means that it is not advisable to run this in a page, in case another function on the page runs a heavy algorithm like face recognition - one would probably want to instantiate a Web worker for isolation, bringing up another host of W3C issues....) -- Surveillance is pervasive. Go Dark.
- [MMUSIC] Information on timer accuracy in browsers Martin Thomson
- Re: [MMUSIC] Information on timer accuracy in bro… Harald Alvestrand