Implement Long Animation Frame API
Categories
(Core :: DOM: Performance, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
platform-rel | --- | + |
People
(Reporter: Harald, Unassigned)
References
()
Details
(Keywords: dev-doc-needed, Whiteboard: [platform-rel-Facebook] [webpagetest])
A new performance API to enable applications to measure responsiveness, by detecting presence of “long tasks” that cause contention on the main thread. References: Spec: https://wicg.github.io/longtasks Explainer: https://github.com/spanicker/longtasks Tag review link: https://github.com/w3ctag/spec-reviews/issues/150 Chrome's Intent to Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Mx9q5WXunSE
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Comment 1•7 years ago
|
||
Long Tasks proposals are being migrated from WICG to WebPerf WG
> Long Tasks API was incubated in WICG and the group has been involved from the start: we discussed it at length at TPAC and been iterating on it since, in our calls and via WICG discussions. Chrome is shipping v1 of the API soon. We intend to migrate and continue work on this spec within WebPerf WG.
Comment 2•7 years ago
|
||
resolved |
I'm interested in smaug's thoughts here but his queue is closed so I'll ask him by email and report back (leaving needinfo on me).
Comment 3•7 years ago
|
||
resolved |
smaug's needinfo queue is open :)
Comment 4•7 years ago
|
||
resolved |
What is the current spec for this? https://w3c.github.io/longtasks/ clearly says "Not Ready For Implementation" and that is from February.
Reporter | ||
Comment 5•7 years ago
|
||
resolved |
(In reply to Olli Pettay [:smaug] from comment #4) > What is the current spec for this? > https://w3c.github.io/longtasks/ clearly says "Not Ready For Implementation" > and that is from February. Fixed in https://github.com/w3c/longtasks/pull/23 Related a discussion on blink-dev: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Mx9q5WXunSE
Updated•7 years ago
|
Reporter | ||
Comment 6•7 years ago
|
||
ni? overholt for prioritization. v1 is in Chrome since 58. Would it make sense to start with a technical review of the spec if there any blockers?
Comment 7•7 years ago
|
||
I'll try to get it into our queue for the next few months. Any more info you can share about usefulness would be appreciated.
Comment 8•7 years ago
|
||
The Activity Stream team is interested in this.
Reporter | ||
Comment 9•7 years ago
|
||
Facebook & LinkedIn both are interested in this. Related, Soasta/Akamai rolled this out on a few sites and shared tips & first insights in a presentation at Fluent in collaboration with Shubhie from Google https://cdn.oreillystatic.com/en/assets/1/event/259/Reliably%20measuring%20responsiveness%20in%20the%20wild%20Presentation.pdf (Long Task started at page 22) This can really help sites to identify the culprits for slow page load and optimize more effectively. This presentation only focuses on page load as it is the easiest to aggregate. I don't agree that Long Task is very interesting for page load as is becomes most important after the page is actually interactive. This API will be even more useful for single page apps, like FB and LinkedIn.
Reporter | ||
Comment 10•7 years ago
|
||
Back to :overholt for prioritizing, considering the new input.
Comment 11•7 years ago
|
||
Thanks! Still P2 as we keep all non-critical-but-important-next-items as P2 but the information is great to facilitate that conversation.
Comment 13•5 years ago
|
||
Comment 14•4 years ago
|
||
Would love to have this in Firefox too. I think the value in the long task API has been proved by the two new metrics derived from Long Tasks: Total Blocking Time and maxPotentialFirstInputDelay.
However I would also like better attribution so when we get a long task, we can understand what's causing it :)
Mass-removing myself from cc; search for 12b9dfe4-ece3-40dc-8d23-60e179f64ac1 or any reasonable part thereof, to mass-delete these notifications (and sorry!)
Updated•3 years ago
|
Updated•2 years ago
|
Comment 17•2 years ago
|
||
plawless, is this perhaps in perf team's todo list.
Marking this p3 to get this out from the triage list.
Updated•2 years ago
|
Comment 18•2 years ago
|
||
This is in our backlog. We'll review it again in our next planning session.
Comment 19•1 year ago
|
||
Given there's a proposal about changing what long task measures, we should wait for that to be finalized before starting the implementation.
Comment 20•2 months ago
|
||
The above proposal (Long Animation Frame API) has been merged to the spec https://w3c.github.io/longtasks/#sec-loaf-timing . This is the one that we are interested.
Instead of implementing Long Task API, I am rephrasing this bug to only implement that particular part.
I've also filed a spec issue to separate Long Animation Frame out
Description
•