Cell Cycle Chrome Experiment slower/choppier on FF than Chrome

NEW
Unassigned

Status

()

defect
P3
normal
7 years ago
4 hours ago

People

(Reporter: humph, Unassigned)

Tracking

Trunk
x86
macOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

7 years ago
I'm not clear if this is gfx or js or what, but we're a lot less smooth than Chrome on http://n-e-r-v-o-u-s.com/cellCycle/  It's using Processing.js with custom shaders.

It would be nice to run as well as Chrome does with this.
Looked okay to me on Nightly when I tried it. Of course, this was a freshly started up browser that was still doing incremental GC, so that could help. Chrome may have been a little better, but it wasn't a staggering difference.
Even without incremental GC, the GCs seem to be compartmental and pretty short (~20ms).
(Reporter)

Comment 3

7 years ago
Might not be js related, and might be worse on Mac, which is what I'm running.  For me, they are totally different experiences in ff vs. chrome.
(Reporter)

Comment 4

7 years ago
Video they made of using it on Chrome: http://vimeo.com/38204725
On this linux machine about 70% is spent in intel graphics drivers.
(Chrome doesn't run on this machine so can't compare)
(In reply to David Humphrey (:humph) from comment #3)
> Might not be js related, and might be worse on Mac, which is what I'm
> running.  For me, they are totally different experiences in ff vs. chrome.

I was also using a Mac. What things were you doing in the demo? I was only spinning around the starting torus, and zooming in and out. Were those problematic for you, or was it more complex things that caused problem?
(Reporter)

Comment 7

7 years ago
Just simple interactions.  For me, ff is just slower at doing everything on the same hardware than Chrome--everything works, but it lags.  I also note on their blog today (i.e., the demo's authors) that they are recommending people use Chrome for it, which says to me that they at least have noticed this, too.
Do you have hardware acceleration enabled?  What does the graphics portion of about:support say?
(Reporter)

Comment 9

7 years ago
0x1002 Device ID0x68a1 WebGL RendererATI Technologies Inc. -- ATI Radeon HD 5750 OpenGL Engine -- 2.1 ATI-1.6.36GPU Accelerated Windows1/1 OpenGL AzureBackendquartz

Both browsers jitter a bit in their framerate, but I'm getting 40-60fps in Chrome and 11-24fps in our Nightly.
David, could you perhaps profile the site. On OSX you have Shark for that.
(Reporter)

Comment 11

7 years ago
For some reason Shark stopped working for me a while back, and I just get hex symbols, even when using the nightly shark builds.  Just me or known issue?
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.