Closed Bug 1649313 Opened 5 years ago Closed 5 years ago

Add a profiler marker for canceled composites (if we bail out because there's nothing to do)

Categories

(Core :: Graphics: WebRender, task)

task

Tracking

()

RESOLVED FIXED
mozilla80
Tracking Status
firefox80 --- fixed

People

(Reporter: mstange, Assigned: mstange)

Details

Attachments

(1 file)

Sometimes we expect 60 fps compositing but encounter frame skips, for example during video playback or during fling scroll animations. In some cases, these frame skips are not caused by slow compositing, but by "missing" compositing - when the "compositor state" at the time of composition indicates that nothing on the screen has changed.

Here's an example from 60 fps YouTube video playback: https://share.firefox.dev/2Zs6X1M
The compositor thread shows CompositeToTarget markers at a consistent 60fps, but the Renderer thread shows many gaps where it does not have Composite markers.

I think it's worth calling out compositor frames where there's "nothing to do" with a profiler marker.

This patch doesn't call out frames where APZ didn't scroll. I think those don't get detected until we get into the Renderer thread.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: