W3C home > Mailing lists > Public > public-web-perf@w3.org > November 2017

Delaying PerformanceEntry dispatch

From: Timothy Dresser <tdresser@chromium.org>
Date: Mon, 27 Nov 2017 13:33:50 +0000
Message-ID: <CAHTsfZCke+3=zuzsr+MqkX_ksvZ0UWqyKoBx5_hquT-FOnusfQ@mail.gmail.com>
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
The Performance Timeline spec states
"The performance timeline task queue
<https://html.spec.whatwg.org/multipage/#task-queue> is a low priority
queue that, if possible, should be processed by the user agent during idle
periods to minimize impact of performance monitoring code." (spec
<https://w3c.github.io/performance-timeline/#queue-a-performanceentry>)
Currently, it looks like all browsers dispatch these tasks immediately.

Chrome is thinking
<https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/TgoXNRtA3Zs>
about
delaying dispatch of most entries to execute during idle time, or with a
100ms delay, whichever comes first.

This aligns with the spec, but given that browser behavior is currently
aligned on delivering entries immediately, we thought we should reach out,
and see if other vendors believe this change is an improvement.

Any thoughts on whether this makes sense, and whether you're likely to add
this delay?

Thanks,
Tim
Received on Monday, 27 November 2017 13:34:27 UTC

This archive was generated by hypermail 2.3.1 : Monday, 27 November 2017 13:34:27 UTC