Closed mithro closed 10 years ago
Is this dupe of issue #1?
No, I believe the intent is to capture the CPU time of the main + compositor threads only. I.e. same as Chrome Devtools provides on paint + layout events.
We'll want to have explicit language that gpu-side costs aren't included. But yeah this is a good bug to talk through the details. Sorry bout the incorrect dupage. :)
Could we also have clear language about this being an estimate? Maybe it's implied with any performance metric?
dupe of #1, closing this.
The spec currently says;
It is my understanding that the intention is for the cpuTime on the PerformanceMainFrameTiming to include all cpu time spent in the system (including in the compositor and other parts of the system) to get this main frame onto the screen. Is that correct?
It is probably worth adding something like "(best?) estimate of" to the description too?