Closed
Bug 1071883
Opened 10 years ago
Closed 9 years ago
Identify add-ons causing lots of CPOW jank using telemetry
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: billm, Unassigned)
References
Details
Similar to bug 1071880, but send the data back using telemetry.
Updated•10 years ago
|
Comment 1•9 years ago
|
||
Maybe add a PROFILER_LABEL call so BHR will report the frame?
Actually, the data is already uploaded with PERF_MONITORING_SLOW_ADDON_CPOW_US. We need post-processing to sort worst offenders.
Updated•9 years ago
|
Blocks: 1224374, e10s-measurement
Updated•9 years ago
|
Blocks: e10s-responsiveness
Comment 3•9 years ago
|
||
CPOW frames show up well in the latest BHR stacks (an example: https://gist.github.com/chutten/1c1df7314f480603a6df ) An analysis using PERF_MONITORING_SLOW_ADDON_CPOW_US should prove useful as well, though it will show heavy CPOW users even if the CPOW doesn't cause jank.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•