Closed Bug 1348989 Opened 9 years ago Closed 3 years ago

D3.js generated graph is much less responsive than in Chrome due to lots of display list/layers overhead

Categories

(Core :: SVG, enhancement, P3)

enhancement

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox55 --- affected

People

(Reporter: jwatt, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: perf)

https://kieranhealy.org/philcites/ Grab and move a node in the graph. In Chrome it's nice and smooth, in Firefox it's noticeably janky. I profile this: https://perfht.ml/2nLHjkP 68% nsDisplayList::PaintRoot 32% ClientContainerLayer::RenderLayer 17% FrameLayerBuilder::ComputeGeometryChangeForItem 11% FrameLayerBuilder::BuildContainerLayerFor 3% LayerPropertiesBase::ComputeDifferences 15% JS So we spend as much time processing layers/display lists as we do actually painting. Interestingly the nodes and text are layerized since they are moved by changing their transforms, but the lines connecting the nodes are not layerized since they are moved by simply changing their vertices.
See Also: → 884787
Priority: -- → P3
Severity: normal → S3

URL is down so it's not possible to test but SVG performance is much better, at least on M1 macs: https://bugzilla.mozilla.org/show_bug.cgi?id=1259142

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.