Confirmed users
1,983
edits
m (talos note) |
(added probe suggestions) |
||
| Line 19: | Line 19: | ||
1) We can't rely on Talos numbers generated in automation for beta builds. The default there is one content process. We'll have to use try runs of the beta code base to generate comparisons. | 1) We can't rely on Talos numbers generated in automation for beta builds. The default there is one content process. We'll have to use try runs of the beta code base to generate comparisons. | ||
2) Probes we might want to add: | |||
{| class="wikitable" | |||
! COMPOSITOR_ANIMATION_MAX_CONTIGUOUS_DROPS_APZ | |||
|style="width:300px;"|For APZ/scrolling compositor animations, the maximum number of contiguous frame drops encountered | |||
|- | |||
! COMPOSITOR_ANIMATION_MAX_CONTIGUOUS_DROPS_CHROME | |||
| For compositor animations of chrome-process layers, the maximum number of contiguous frame drops encountered | |||
|- | |||
! COMPOSITOR_ANIMATION_MAX_CONTIGUOUS_DROPS_CONTENT | |||
| For compositor animations of content-process layers, the maximum number of contiguous frame drops encountered | |||
|- | |||
! TIME_TO_NON_BLANK_PAINT_MS | |||
| The time between navigation start and the first non-blank paint of a foreground root content document, in milliseconds. This only records documents that were in an active docshell throughout the whole time between navigation start and non-blank paint. The non-blank paint timestamp is taken during display list building and does not include rasterization or compositing of that paint. | |||
|} | |||
= Release Criteria = | = Release Criteria = | ||