Closed Bug 1506976 Opened 11 months ago Closed 8 months ago
Add telemetry and profiler markers for Time-to-First
Contentful Paint Composite End: measure until the composition for the paint has completed, and not just until display list building
47 bytes, text/x-phabricator-request
|Details | Review|
We have various pieces of instrumentation for measuring page load until a certain paint. At the moment, all these paint measurements take their "end" timestamp at the time the display list for that paint is built. However, this skips a large part of the painting pipeline: tile allocation, rasterization (which can happen on a different thread), time until the transaction is processed in the compositor thread's event queue, compositing. We should build upon the framework from bug 1501442 to obtain the correct timestamp here. This will have two advantages: - The measured value reflects reality more closely. - It's easier to associate these timings / markers with screenshots taken in the compositor. This makes it easier to assess their validity. Especially the latter is really hard to do correctly with the current setup.
Assignee: nobody → mstange
Status: NEW → ASSIGNED
Priority: P3 → P1
Summary: Make non-blank paint instrumentation and friends (DomContentFlushed, TTFCP) measure until the composition for the paint has completed, and not just until display list building → Add telemetry and profiler markers for Time-to-FirstContentfulPaintCompositeEnd: measure until the composition for the paint has completed, and not just until display list building
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/c27aa490f40b Make FirstContentfulPaint timing measure until the composite end of the paint. r=bas
You need to log in before you can comment on or make changes to this bug.