Closed Bug 1606878 Opened 5 years ago Closed 2 years ago

Add PerfStats for time spent in Gecko composition recorder

Categories

(Core :: Performance, enhancement, P5)

enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: nalexander, Unassigned)

References

Details

Bug 1536174 added Gecko support for capturing rendered frames: the composition recorder. It's unclear what the performance overhead is of such recording. This ticket tracks using the small framework for capturing granular perf stats with low-overhead added by Bug 1553254 to measure that overhead.

There are two interesting things I'd like to see from this measurement. Obviously, I'm curious to know what the measured overhead is. But we might also be able to see a larger overhead across compound actions, for example, across an entire pageload. That might suggest the actual impact of reserving memory for the frames captured by the composition recorder.

Bas: I've written this as a ticket around PerfStats, but it's not really necessary to use that framework. Is it foolish to do so? Is there a better way to capture that data?

Flags: needinfo?(bas)

(In reply to Nick Alexander :nalexander [he/him] from comment #1)

Bas: I've written this as a ticket around PerfStats, but it's not really necessary to use that framework. Is it foolish to do so? Is there a better way to capture that data?

It doesn't seem crazy to be.. it feels like the kind of thing that perf stats should be well suited to measure!

Flags: needinfo?(bas)
Priority: -- → P5

I'm going to close this bug since we are mostly using ffmpeg for screen capture and moving away from the screen recorder.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.