Closed Bug 1395184 Opened 8 years ago Closed 7 years ago

Creating WebRender display list is slow on MazeSolver

Categories

(Core :: Graphics: WebRender, defect, P3)

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox56 --- unaffected
firefox57 --- unaffected

People

(Reporter: mstange, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [wr-reserve])

https://testdrive-archive.azurewebsites.net/Performance/MazeSolver/Default.html Profile with webrender: http://bit.ly/2wT0nVX Profile with webrender + layers-free: http://bit.ly/2wSA8io It takes around 28ms to convert the layer tree or the display list to the webrender display list. That's almost as slow as FrameLayerBuilder.
It looks like this is mostly mozilla::layers::ScrollingLayersHelper::ScrollingLayersHelper. Can we do something to make that a lot cheaper?
Flags: needinfo?(bugmail)
We also do an extra push_built_display_list for no real good reason. We should be able to take that out without much trouble.
(In reply to Jeff Muizelaar [:jrmuizel] from comment #1) > It looks like this is mostly > mozilla::layers::ScrollingLayersHelper::ScrollingLayersHelper. Can we do > something to make that a lot cheaper? Yeah I put a patch on bug 1395212.
Flags: needinfo?(bugmail)
Priority: P3 → P2
Whiteboard: [wr-mvp]
Priority: P2 → P3
Whiteboard: [wr-mvp] → [wr-reserve]
This is pretty good these days. The RenderLayers marker in the profiler is between 3 and 4ms on MazeSolver now. https://perfht.ml/2A1SRdK
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.