1636180 - Lower fps than Chrome with this canvas test

Status: NEW

(Core :: Graphics: Canvas2D, defect)

Description

[Andrew Overholt [:overholt]]

Attachment: about:support

On Windows 10 I get 50-60 fps in Chrome release (about 30 fps with the Paper.js example) Click the various frameworks to switch between them. I only get ~40-50 fps in Nightly with WebRender (and Fission).

https://benchmarks.slaylines.io/two.html

Comment 1

[Bob Owen (:bobowen)]

(In reply to Andrew Overholt [:overholt] from comment #0)
...

On Windows 10 I get 50-60 fps in Chrome release (about 30 fps with the Paper.js example) Click the various frameworks to switch between them. I only get ~40-50 fps in Nightly with WebRender (and Fission).

Out of interest, what is the performance like on Firefox release (without remote canvas)?

Comment 2

[Mayank Bansal]

Win10+WR+Remote Canvas
PixiJS(60FPS) : https://perfht.ml/3beYliy
PaperJS (20FPS) : https://perfht.ml/2znnU3G
TwoJS(30FPS) : https://perfht.ml/2WdCUKQ

Win10+WR+Remote Canvas disabled

PixiJS(60FPS) : https://perfht.ml/2SNgvSp
PaperJS (15FPS) : https://perfht.ml/2WAiIS9
TwoJS(30FPS) : https://perfht.ml/3ftlRM6

Conclusion: With remote canvas disabled, perf is slightly worse in PaperJS.
TwoJS looks JS bound?

Comment 3

[Andrew Overholt [:overholt]]

(In reply to Bob Owen (:bobowen) from comment #1)

(In reply to Andrew Overholt [:overholt] from comment #0)
...

On Windows 10 I get 50-60 fps in Chrome release (about 30 fps with the Paper.js example) Click the various frameworks to switch between them. I only get ~40-50 fps in Nightly with WebRender (and Fission).

Out of interest, what is the performance like on Firefox release (without remote canvas)?

All with a Count of 1000 and the Nightly numbers are about the same with Fission.

Paper.js: low-mid 20s
PixiJS: 58-60
Two.js: high 30s

Compared with the following in Nightly:

Paper.js: ~12
PixiJS: mid 40s sometimes peaking at 60
Two.js: mid 30s