Open
Bug 1888027
(wr-scroll-perf)
Opened 6 months ago
Updated 22 days ago
[meta] [project] Fix performance issues when scrolling
Categories
(Core :: Graphics: WebRender, task)
Core
Graphics: WebRender
Tracking
()
NEW
People
(Reporter: gw, Assigned: nical)
References
(Depends on 47 open bugs, Blocks 3 open bugs)
Details
(Keywords: meta)
No description provided.
Assignee | ||
Updated•5 months ago
|
Depends on: wr-gpu-time
Assignee | ||
Updated•5 months ago
|
Depends on: wr-renderer-perf
Assignee | ||
Updated•5 months ago
|
Depends on: wr-batching-perf
Assignee | ||
Updated•5 months ago
|
Depends on: sw-wr-perf
Assignee | ||
Updated•5 months ago
|
Depends on: wr-svg-filter-perf
Assignee | ||
Updated•5 months ago
|
Depends on: texture-upload-perf
Updated•5 months ago
|
Depends on: picture-cache-perf
Reporter | ||
Updated•5 months ago
|
Rank: 2
Reporter | ||
Updated•5 months ago
|
Severity: -- → S2
Updated•4 months ago
|
Assignee: nobody → nical.bugzilla
Assignee | ||
Comment 2•4 months ago
|
||
We have a fair amount of bugs on file about cases where we fail to meet the frame budget during scrolling or animations. These are the most noticeable types of frame drops (as opposed to, for example, when the first frame of a document takes more than 16ms to be produced), so efforts focusing these missed scrolling/animating frames are likely to have a noticeable user impact.
The first step is to classify and investigate the most common sources of scroll jank. We recently added some tooling to classify slow scrolling/animation frames caused by CPU-side performance issues and display the breakdown in WebRender's profiler overlay. Next steps include:
- Add more granularity to the classification.
- Expose the data via telemetry probes.
- Triage, classify and prioritize the test cases in the dependency tree of this bug.
- Fix issues identified by the above three steps.
You need to log in
before you can comment on or make changes to this bug.
Description
•