We need to record the reflows on a per app basis for architecture validation purposes. This would be stored as a histogram and delivered as a ping to the Telemetry Server.
Jan, how much work would do you think it would be to track reflows per context/frame?
(I'll have a better reply soon, see also https://bugzilla.mozilla.org/show_bug.cgi?id=1166286#c2)
Referring to the bug title, tracking reflows per app is already something the HUD can do, so it will be pretty easy (with bug 1166295) to feed that data to Telemetry. It might be possible to get a more precise origin for a reflow. I imagine we hear about reflows from a particular renderer, so the console devtools actor that listens for reflows could in theory also tell which renderer performed a particular reflow. Per-app (actually per-frame, or better per-top-level-content) measurements is something that the HUD already knows how to do, so maybe let's do that for now. For the Telemetry metrics where it's really important to know from which precise context (e.g. from which worker or iframe inside that top-level-content) an event was triggered, let's file bugs to make the associated devtools actor context-aware. I can help with the bug filing, because I know which devtools actor is responsible for which HUD metric.
Assignee: nobody → rnicoletti
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1183101
You need to log in before you can comment on or make changes to this bug.