Open Bug 1247603 Opened 9 years ago Updated 2 years ago

WebGL performance in Sponza by Babylon.js WebGL demo.

Categories

(Core :: Graphics: CanvasWebGL, defect, P3)

47 Branch
x86_64
Windows 10
defect

Tracking

()

Tracking Status
firefox47 --- affected

People

(Reporter: jujjyl, Unassigned)

Details

(Keywords: perf, Whiteboard: gfx-noted)

STR: Visit http://www.babylonjs.com/demos/SponzaDynamicShadows/ Observed: Both Chrome 48.0.2564.103 m and Edge 25.10586.0.0 run at 60fps. In Firefox Nightly 64-bit 47.0a1 (2016-02-10), framerate is around 21-30fps. In Firefox 32-bit 44.0 stable, framerate is slightly better hovering around 35-40fps. Tested on HASWELL ------- Custom built desktop PC Windows 10 Home 64-bit 3.0 GHz Intel 8-Core i7-5960X 32GB of RAM 3840x2160 pixels display SLI 2x ASUS NVIDIA GeForce GTX 980 Ti, 12GB of RAM, driver version 361.75 - nvd3dumx.dll, nvwgf2umx.dll: - version 10.18.13.6175 - date 1/22/2016 - D3D Version 12.1, WDDM 2.0, WHQL approved
This issue may be related to the graphics regression at bug 1247585.
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
I am getting rock solid 60 FPS on my Macbook Pro in both Firefox 44 and Chrome 48.0.2564.109 (64-bit). Just reporting per Jukka suggestion as this may point to Windows only/ANGLE problem. This is a beefy machine with both the Iris Pro and nVidia secondary GPU FWIW.
Whiteboard: gfx-noted,perf
Tested. I am averaging 24FPS and never hits 30FPS+ on my MacBook Pro 13" using Firefox 44.0.1. Other build info: * 2.8 GHz Intel Core i7 * 16 GB 1600 MHz DDR3 * Intel Iris 1536 MB Screenshot: https://www.dropbox.com/s/qid28mfhzivekkk/Screenshot%202016-02-11%2010.36.45.png?dl=0
If you set the webgl.enable-prototype-webgl2 preference to false in about:config do things improve?
(In reply to Jeff Muizelaar [:jrmuizel] from comment #4) > If you set the webgl.enable-prototype-webgl2 preference to false in > about:config do things improve? It's value is already set to false. Ironically if I do set the preference to 'true' — the assets don't load. * Screenshot: https://www.dropbox.com/s/qfd8gmmfx35s40x/Screenshot%202016-02-11%2019.03.07.png?dl=0
(In reply to Desigan Chinniah [:cyberdees] [:dees] [London - GMT] from comment #5) > (In reply to Jeff Muizelaar [:jrmuizel] from comment #4) > > If you set the webgl.enable-prototype-webgl2 preference to false in > > about:config do things improve? > > It's value is already set to false. > > Ironically if I do set the preference to 'true' — the assets don't load. > * Screenshot: > https://www.dropbox.com/s/qfd8gmmfx35s40x/Screenshot%202016-02-11%2019.03.07. > png?dl=0 Oh sorry, I didn't realize you were using FF44. Is there a version that you see a performance regression compared to?
(In reply to Jeff Muizelaar [:jrmuizel] from comment #6) > (In reply to Desigan Chinniah [:cyberdees] [:dees] [London - GMT] from > comment #5) > > (In reply to Jeff Muizelaar [:jrmuizel] from comment #4) > > > If you set the webgl.enable-prototype-webgl2 preference to false in > > > about:config do things improve? > > > > It's value is already set to false. > > > > Ironically if I do set the preference to 'true' — the assets don't load. > > * Screenshot: > > https://www.dropbox.com/s/qfd8gmmfx35s40x/Screenshot%202016-02-11%2019.03.07. > > png?dl=0 > > Oh sorry, I didn't realize you were using FF44. Is there a version that you > see a performance regression compared to? No. However Comment 2 from Andre is likely from very similar hardware and also on using Stable 44.
Yep.
Keywords: perf
Whiteboard: gfx-noted,perf → gfx-noted
On the HASWELL computer above: 64-bit FF Nightly 47.0a1 (2016-02-11), e10s enabled: ~30fps 64-bit FF Nightly 47.0a1 (2016-02-11), e10s disabled: 60fps 64-bit FF Nightly 47.0a1 (2016-02-11), e10s enabled and webgl.enable-prototype-webgl2;false: 60fps. 64-bit FF Nightly 47.0a1 (2016-02-11), e10s enabled and webgl.bypass-shader-validation;true and webgl.disable-angle;true: ~30fps
Given comment 9 and comment 2, should this be tagged as "with E10S enabled"?
I get 60fps Windows 7 SP1, 32-bit Firefox 44. Quadro 600.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.