Surface Long Tasks in DevTools |
|||||||
Issue descriptionFor diagnosis, it would be great if developers could directly get a view of long tasks (surfaced from the API) in DevTools. Currently this surfaces with FPS / slow frame red warning and script / layout etc breakdown This is fine, but directly indicating long tasks would be a good addition and unify / strengthen our message of Long Tasks as perpetrators of responsiveness issues. Thoughts? Record a profile on this demo to get an idea: https://wicg.github.io/longtasks/render-jank-demo.html
,
Aug 2 2017
Andrey, any thoughts on whether devtools would consider exposing this?
,
Nov 15 2017
,
Feb 28 2018
I'll bring this up at the next Chrome Speed Metrics meeting.
,
Mar 22 2018
Current proposal: Add a separate track (like above frames) that is "Tasks" or "Long Tasks". In it we place new boxes for long tasks. They represent scheduler-level tasks (ThreadControllerImpl::DoWork). We probably only show ones that are long (>50ms) and maybe add more red color as their duration increases.
,
Jul 3
,
Dec 5
DevTools is presenting long tasks already in the form of: - console log violations and - warning markers on the performance timeline
,
Dec 5
I believe the warning markers on the performance timeline use a different definition of task than Chrome's scheduler, which means that you can block the main thread for long periods of time without getting warnings. Is this not the case?
,
Dec 5
That's true. the precise definition of long tasks used in scheduler/longtasksapi is not conveyed in the timeline.
,
Dec 5
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by caseq@chromium.org
, Jan 17 2017Status: Assigned (was: Untriaged)