W3C home > Mailing lists > Public > public-web-perf@w3.org > January 2018

Re: Temporarily reducing precision of DOMHighResTimeStamp in Chrome

From: Ben Maurer <ben.maurer@gmail.com>
Date: Mon, 8 Jan 2018 08:15:41 -0800
Cc: public-web-perf@w3.org
Message-Id: <66F78B8A-DFA6-4DEF-B32A-555080E44F98@gmail.com>
To: Ross McIlroy <rmcilroy@google.com>
Will the time stamps be monotonic? 

Sent from my iPhone

> On Jan 8, 2018, at 4:22 AM, Ross McIlroy <rmcilroy@google.com> wrote:
> 
> As part of our mitigations against Speculative Side Channel Attacks, Chrome 64 will reduce the resolution of DOMHighResTimeStamps to 100us. We are also introducing 100us of random jitter to the clock edges to prevent attempts to increase resolution via edge-thresholding.  The returned time will be within +/100us of real time, however there will be no guarantee as to duration (in real time) of clock pulses between these 100us intervals.
> 
> We intend for this to be a temporary measure while other mitigation are introduced, however we do not have a timeline for restoring the previous precision. 
> 
> Ross / Sami
> 
Received on Monday, 8 January 2018 16:16:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 8 January 2018 16:16:06 UTC