Open
Bug 1508116
Opened 6 years ago
Updated 2 years ago
4-5ms spent scene building new Gmail (scene building is too slow)
Categories
(Core :: Graphics: WebRender, defect, P3)
Core
Graphics: WebRender
Tracking
()
NEW
People
(Reporter: jrmuizel, Unassigned)
References
(Blocks 3 open bugs)
Details
STR:
- put the new gmail in compact mode
- move the mouse over a bunch of rows
https://perfht.ml/2KaMLcw
Half of the time (54%) is spent in realloc.
Another 10% is spent in malloc.
Reporter | ||
Updated•6 years ago
|
Blocks: stage-wr-trains
Priority: -- → P2
Reporter | ||
Updated•6 years ago
|
Depends on: content-full-paint-time
Reporter | ||
Updated•6 years ago
|
Blocks: content-full-paint-time
No longer depends on: content-full-paint-time
This ties into the profiling work I and :gw have been doing. I'm currently working on refactoring WR SceneBuilder to alleviate the realloc/malloc hit.
The work on the issues will be tracked in WR Github issues.
Assignee: nobody → dglastonbury
Reporter | ||
Updated•6 years ago
|
Summary: 6-7ms spent scene building new Gmail → 6-7ms spent scene building new Gmail (scene building is too slow)
Reporter | ||
Comment 2•6 years ago
|
||
Is there more work we anticipate doing here?
Flags: needinfo?(dglastonbury)
@jrmuizel there is more work that I want to do to remove the last realloc/malloc churn I saw in the WR backend.
Flags: needinfo?(dglastonbury)
I just profiled on my macOS and gmail looks really smooth. No dropped frames. Each thread spending 99% idle. So I'd be happy to close this bug, @jrmuizel.
Flags: needinfo?(jmuizelaar)
Reporter | ||
Comment 5•6 years ago
|
||
I still have an appreciable amount of time in scene building on gmail. https://perfht.ml/2C6ljJf
But happy to make this not block.
Flags: needinfo?(jmuizelaar)
Summary: 6-7ms spent scene building new Gmail (scene building is too slow) → 4-5ms spent scene building new Gmail (scene building is too slow)
Updated•4 years ago
|
Blocks: wr-scene-building
Updated•4 years ago
|
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•