Attention is currently required from: Paul Irish, Yang Guo.
Philip Rogers would like Yang Guo and Paul Irish to review this change.
Add the new "Layerize" devtools timeline event (chromium side)
Layerize is the step of the rendering pipeline where we decide which
layers to create [1]. It is the second most expensive step in the
pipeline [2] which is why it is important to not have it show a blank
space on the devtools timeline. This event is also actionable using the
"Layers" panel, or other knowledge of what "creates a layer".
This is a followup to a front-end patch:
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4117136
This patch implements the code to emit the new layerize event. This is
recorded alongside the UMA event that the team uses to track
performance of this function (that UMA metric is unfortunately called
CompositingCommit).
[1] https://developer.chrome.com/articles/renderingng-architecture/
[2] https://uma.googleplex.com/p/chrome/timeline_v2?sid=d57f93f88aad2b81484351dca9cd716f
Bug: 1191032
Change-Id: If834ac65d55482fe7406652a97d5c17a6f7973e8
---
M third_party/blink/renderer/core/frame/local_frame_view.cc
M third_party/blink/renderer/core/inspector/inspector_trace_events.cc
M third_party/blink/renderer/core/inspector/inspector_trace_events.h
A third_party/blink/web_tests/http/tests/devtools/tracing/timeline-paint/timeline-layerize-expected.txt
A third_party/blink/web_tests/http/tests/devtools/tracing/timeline-paint/timeline-layerize.js
5 files changed, 90 insertions(+), 0 deletions(-)
To view, visit change 4118117. To unsubscribe, or for help writing mail filters, visit settings.
Attention is currently required from: Paul Irish, Yang Guo.
1 comment:
Patchset:
Paul or Yang, would either of you be good reviewers for this and the front-end patch (https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4117136)?
To view, visit change 4118117. To unsubscribe, or for help writing mail filters, visit settings.
Attention is currently required from: Xianzhu Wang.
Philip Rogers would like Xianzhu Wang to review this change.
Add the new "Layerize" devtools timeline event (chromium side)
Layerize is the step of the rendering pipeline where we decide which
layers to create [1]. It is the second most expensive step in the
pipeline [2] which is why it is important to not have it show a blank
space on the devtools timeline. This event is also actionable using the
"Layers" panel, or other knowledge of what "creates a layer".
This is a followup to a front-end patch:
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4117136
This patch implements the code to emit the new layerize event. This is
recorded alongside the UMA event that the team uses to track
performance of this function (that UMA metric is unfortunately called
CompositingCommit).
[1] https://developer.chrome.com/articles/renderingng-architecture/
[2] https://uma.googleplex.com/p/chrome/timeline_v2?sid=d57f93f88aad2b81484351dca9cd716f
Bug: 1191032
Change-Id: If232c0c10d57a5393e7428ea84eaed7257d69765
---
M third_party/blink/renderer/core/frame/local_frame_view.cc
M third_party/blink/renderer/core/inspector/inspector_trace_events.cc
M third_party/blink/renderer/core/inspector/inspector_trace_events.h
3 files changed, 40 insertions(+), 0 deletions(-)
To view, visit change 4118927. To unsubscribe, or for help writing mail filters, visit settings.
Attention is currently required from: Xianzhu Wang.
Patch set 3:Commit-Queue +1
Attention is currently required from: Philip Rogers.
Patch set 3:Code-Review +1
Attention is currently required from: Philip Rogers.
Patch set 3:Commit-Queue +2
Chromium LUCI CQ submitted this change.
Add the new "Layerize" devtools timeline event (chromium side)
Layerize is the step of the rendering pipeline where we decide which
layers to create [1]. It is the second most expensive step in the
pipeline [2] which is why it is important to not have it show a blank
space on the devtools timeline. This event is also actionable using the
"Layers" panel, or other knowledge of what "creates a layer".
This is a followup to a front-end patch:
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4117136
This patch implements the code to emit the new layerize event. This is
recorded alongside the UMA event that the team uses to track
performance of this function (that UMA metric is unfortunately called
CompositingCommit).
[1] https://developer.chrome.com/articles/renderingng-architecture/
[2] https://uma.googleplex.com/p/chrome/timeline_v2?sid=d57f93f88aad2b81484351dca9cd716f
Bug: 1191032
Change-Id: If232c0c10d57a5393e7428ea84eaed7257d69765
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4118927
Reviewed-by: Xianzhu Wang <wangx...@chromium.org>
Commit-Queue: Philip Rogers <p...@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1086503}
---
M third_party/blink/renderer/core/frame/local_frame_view.cc
M third_party/blink/renderer/core/inspector/inspector_trace_events.cc
M third_party/blink/renderer/core/inspector/inspector_trace_events.h
3 files changed, 44 insertions(+), 0 deletions(-)
Philip Rogers abandoned this change.
To view, visit change 4118117. To unsubscribe, or for help writing mail filters, visit settings.