Chrome is more responsive on the D3.js based MIT Media Lab's Immersion application




5 years ago
2 months ago


(Reporter: birtles, Unassigned)


(Blocks: 1 bug, {parity-chrome, perf})

parity-chrome, perf
Dependency tree / graph

Firefox Tracking Flags

(firefox56 affected)


(Whiteboard: [in-the-wild] [qf:p3:responsiveness], URL)



5 years ago
At MozFest 2013, Deepak Jagdish introduced me to MIT Media Lab's Immersion application which uses SVG to visualize social connections.

They are currently using Chrome to demo the application since the animation of SVG shapes is too slow on Firefox.

If you load the URL in Chrome the animation is very smooth and responsive. In Firefox it is very jittery and uses a lot of CPU.
FWIW, SPS profile against Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140321030203 CSet: 72c2f9ebf4bc:

(played with the "Charge", "Nodes" and "Links" sliders)

This is - again - slow D3.js perf.
I put the Nodes slider to maximum and jiggle the Links slider around I can still see Chrome is a bit smoother. That said, there's a big improvement since we started the Moz2D work.
Bug 1090934 should also help a bit more.
Depends on: 1090934
I'm going to close this, but it would be good if you could check you're happy with that, Brian.
Last Resolved: 2 years ago
Flags: needinfo?(bbirtles)
Resolution: --- → WORKSFORME
Summary: Immersion animation of SVG is slow → Chrome is more responsive on the D3.js based MIT Media Lab's Immersion application

Comment 5

2 years ago
Chrome still seems significantly smoother to me. When you click a circle we drop a lot of frames and only the second half of the transition animates. When I drag the slider I get about half the frame rate of Chrome.
Flags: needinfo?(bbirtles)
Resolution: WORKSFORME → ---
Whiteboard: [in-the-wild] [parity-chrome] → [in-the-wild] [parity-chrome][qf:investigate]
Blocks: 1262352
status-firefox56: --- → affected
OS: Windows 7 → All
Priority: -- → P2
Hardware: x86_64 → All
Flags: needinfo?(cku)


2 years ago
Depends on: 1385159


2 years ago
Depends on: 1385164
Flags: needinfo?(cku)


2 years ago
Assignee: nobody → cku

Comment 7

2 years ago
Turing on webrender make perfromance worse...
(In reply to C.J. Ku[:cjku](UTC+8) from comment #7)
> Turing on webrender make perfromance worse...

A bug worth checking further.
Flags: needinfo?(howareyou322)
Flags: needinfo?(howareyou322)

Comment 9

2 years ago
Painting - 8 ~ 9 ms
Scripts - 4.8 ms in average. 
DisplayList - 1ms in average
LayerBuilding - 2~3 ms
Reflows - 0.3 ms
Styles - 0.4 ms

FF FPS is around 55, and Chrome can render frames in 60FPS constantly.

Comment 10

2 years ago
As per comment 5 I see a lot of dropped frames on Windows when you click the circles to expand/collapse them but I don't see (m)any dropped frames in Chrome, and even Edge seems better.


2 years ago
Depends on: 1385861


a year ago
Assignee: cku → nobody
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome
Whiteboard: [in-the-wild] [parity-chrome][qf:investigate] → [in-the-wild] [qf:investigate]
The delay when clicking a circle, at least on Mac, is dominated by tile allocation. It seems like we're creating too many layers and not reusing tiles effectively. I've filed bug 1514047 about the WebRender part of this.
Component: SVG → Graphics: Layers
Whiteboard: [in-the-wild] [qf:investigate] → [in-the-wild] [qf]
Whiteboard: [in-the-wild] [qf] → [in-the-wild] [qf:p3:responsiveness]
You need to log in before you can comment on or make changes to this bug.