New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 704926 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocked on:
issue 697758



Sign in to add a comment

Building shaders seems slow in Chrome compared to Firefox

Project Member Reported by ahaas@chromium.org, Mar 24 2017

Issue description

Chrome Version: (59.0.3051.0)
OS: Linux (Goobuntu)

What steps will reproduce the problem?
(1) Open https://s3.amazonaws.com/mozilla-games/ZenGarden/EpicZenGarden.html in Chrome and in Firefox nightly.
(2) Compare the times it takes to build the shaders

What is the expected result?
That Chrome is faster than Firefox.

What happens instead?
Firefox is faster than Chrome.

Careful: The WebAssembly compilation time seems to be included in the shader building time. Without WebAssembly compilation time, building the shaders takes 12,85 seconds on Chrome and 4,6 seconds on Firefox on my Z840.
 

Comment 1 by ahaas@chromium.org, Mar 24 2017

Cc: seththompson@chromium.org
Owner: kbr@chromium.org
Hi Ken,
Is this your area of expertise? Can you take a look?
Thanks, Andreas

Comment 2 by kbr@chromium.org, Mar 24 2017

Blockedon: 697758
Cc: lethalantidote@chromium.org
Components: Blink>WebGL
Labels: OS-All
Owner: ----
Status: Available (was: Untriaged)
Yes. However it would be ideal if we could minimize this test case. Issue 697758 has a minimized test that focuses on shader compilation. Let's see whether that runs faster in Firefox vs. Chrome.

Comment 3 by kbr@chromium.org, Mar 24 2017

Components: Blink>JavaScript>WebAssembly
Owner: ahaas@chromium.org
Status: Assigned (was: Available)
Actually, looking at the other bug, shader compilation time has already been compared between Chrome and Firefox, and the time is comparable. We need to figure out what exactly the Epic Zen Garden demo is doing when it displays "Compiling shaders". Andreas, I'm giving this bug back to you to investigate that.

Status: WontFix (was: Assigned)
This issue is out-dated by now.

Sign in to add a comment