Closed
Bug 1690619
Opened 5 years ago
Closed 4 years ago
Add profiler markers with a simple reason string for composite requests
Categories
(Core :: Gecko Profiler, task, P3)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
95 Branch
People
(Reporter: florian, Assigned: nical)
References
Details
Attachments
(2 files)
The parent process is using continuously more than 30% of a core (10+% just for the main thread), and there's no straightforward way to figure out why.
Markus, any idea about things we could do to make profiles of issues like this more actionable?
Flags: needinfo?(mstange.moz)
Severity: -- → N/A
Priority: -- → P3
Comment 1•5 years ago
|
||
We could:
- Capture stacks in
CompositorVsyncScheduler::ScheduleComposition()and inCompositorBridgeParent::ScheduleRenderOnCompositorThread()(and put those markers on the compositor thread, because the latter function can be called on other threads like the scene builder thread) - Have markers for compositor animations, bug 1343220
- Have markers for APZ animations (say which animations caused
AdvanceAnimationsto return true) - On each CompositeToTarget marker, list which animations are running, so that we see them even if we missed the animation's start marker
- On each CompositeToTarget marker, list which parts of
generateFramearetrue
Flags: needinfo?(mstange.moz)
| Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → nical.bugzilla
Attachment #9243941 -
Attachment description: WIP: Bug 1690619 - WIP - Keep track of where the request to rendering something comes from. → Bug 1690619 - Keep track of where the request to rendering something comes from. r=#gfx-reviewers
Status: NEW → ASSIGNED
| Assignee | ||
Updated•4 years ago
|
Keywords: leave-open
Pushed by nsilva@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/023918f7faca
Keep track of where the request to rendering something comes from. r=gfx-reviewers,mstange
Comment 5•4 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 6•4 years ago
|
||
Pushed by nsilva@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/18ea7a785e83
Fix typos in the RenderReasons profiler integration. r=gfx-reviewers,aosmond
Comment 8•4 years ago
|
||
| bugherder | ||
Comment 9•4 years ago
|
||
I'm going to close this bug. I've filed bug 1736871 to track more follow-up work. "leave-open" bugs make tracking hard.
No longer blocks: 1690673
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox94:
--- → wontfix
status-firefox95:
--- → fixed
Keywords: leave-open
OS: Unspecified → All
Hardware: Unspecified → All
Resolution: --- → FIXED
Summary: Profiles should contain enough informations to understand why compositing happens at 60Hz → Add profiler markers with a simple reason string for composite requests
Target Milestone: --- → 95 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•