Open Bug 1308229 Opened 8 years ago Updated 6 months ago

Categories

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

defect

Tracking

()

People

(Reporter: asa, Unassigned)

References

(Blocks 3 open bugs, )

Details

(Whiteboard: [gfx-noted])

Attachments

(2 files)

From twitter thread https://twitter.com/anatudor/status/784016899722113026 I tested https://codepen.io/thebabydino/full/LRZvdN/ and it is indeed choppy in Firefox and smoother in Chrome.
Component: General → Graphics
Each hex tile is 3d transformed, so this generates a crazy number of layers. Most of which seem to be optimised to colour layers so there probably isn't that much painting going on. So the slowness might come from the compositor side, or from actually sending that many layers to the compositor.
Priority: -- → P3
Whiteboard: [gfx-noted]
Attached file layer-dump.txt
Here's a layer dump. Trying to get a profile but having some problems with the profiler.
Attached file profile
The profile shows we spend a lot of time in FrameLayerBuilder, and a lot of time in ForwardTransaction
On the compositor time we're spending time all over the place. Some low hanging fruit is probably available in LayerPropertiesBase::ComputeDifferences() - 12.3% and LayerManagerComposite::PostProcessLayers() - 11.6%
Severity: normal → S3
Component: Graphics → Graphics: WebRender
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: