User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101203 Firefox/4.0b8pre (id: 20101204020222) The Field and Aquarium demos have lower FPS if ANGLE is enabled. Using default settings in the demos. With ANGLE: Aquarium: 27 Field: 30 webgl.prefer_gl=true: Aquarium: 39 Field: 60 Reproducible: Always ATI Radeon HD 4650 Catalyst 10.11 driver

I can confirm this. Using the flag above webgl.prefer_gl=true. Aquarium with ANGLE: 13 Aquarium w/o ANGLE: 25 ATI Radeon HD 5750 Catalyst 10.10e driver

mm. We need to investigate where the perf slowdown is coming from. However, using ANGLE allows us to bypass a really expensive readback when using a D3D9/D3D10 layer manager; we aren't doing that yet, though.

Vlad, just make sure we're not doing something stupid with ANGLE, and that it's not doing something stupid, and then unblock on this.

It's definitely doing something stupid. Upstream bug is http://code.google.com/p/angleproject/issues/detail?id=89

I don't think I'd block on that fix, but I'm willing to listen to alternative positions. (I do want the fix though, and I'd approve it!)

In https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/sdk/demos/google/nvidia-vertex-buffer-object/index.html ANGLE: 17.82 frames per second 3325741.78 vertices generated per second Slideshow-like. GL: 29.67 frames per second 5536982.64 vertices generated per second

Guys, why are u using ANGLE with AMD GPUs wich have appropriate drivers since Catalyst 10.8? I made some experiences with Google Body Browser HD 4330: GL: superfast ANGLE: slaggish 8800GT GL: total slaggish unusable ANGLE: little slaggish I suggest to whitelist drivers from 10.8, maybe combined with the GPU.

On Windows, D3D is used for compositing, hence once comment 2 is implemented, there's inherent benefit in using ANGLE for WebGL as that interoperates better with it --- unless AMD supports an extension for GL-D3D interop.

(In reply to comment #8) > On Windows, D3D is used for compositing, hence once comment 2 is implemented, > there's inherent benefit in using ANGLE for WebGL as that interoperates better > with it --- unless AMD supports an extension for GL-D3D interop. Forget my previous comment - i made a mistake with the testing. WebGL is solver than GL on both cards... Can you look at Bug 615976, please?

Bug 618892 is fixed, but FPS is still lower with ANGLE. In the Field demo, GL: 40, ANGLE: 25.

I have the same problem with Firefox 8.0a2 (Windows 7 x86_64, NVIDIA 230GT) In this demo (http://www.ibiblio.org/e-notes/webgl/deflate/shark_anim.html) I get 20 FPS more than ANGLE.

No issue with Nightly 10.0 a1 (rev: 46a6d0fd13d5), system nvidia GTX 460 1 GB with forceware 285.38. On Aquarium with ANGLE: I am getting steady 64 fps while minimum drop was at 48 fps. This is with 1000 fish with all turned on. ANGLE is turned ON. Adapter Description: NVIDIA GeForce GTX 460 Vendor ID: 10de Device ID: 0e22 Adapter RAM: 1024 Adapter Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Driver Version: 8.17.12.8538 Driver Date: 9-22-2011 Adapter RAM (GPU #2): Unknown Adapter Drivers (GPU #2): Unknown Direct2D Enabled: true DirectWrite Enabled: true (6.1.7601.17563) ClearType ParametersGamma: 2200 Pixel Structure: RGB ClearType Level: 0 Enhanced Contrast: 400 WebGL Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GTX 460) -- OpenGL ES 2.0 (ANGLE 0.0.0.774) GPU Accelerated Windows: 1/1 Direct3D 10 Latest ANGLE revision is 794.

Ahmad, what are the results with OpenGL instead of ANGLE?

Does webgl.prefer_gl same as webgl.prefer-native_gl? I am getting later on preference in about:config.

^I think its same since in about:suuport now WebRenderer: NVIDIA Corporation -- GeForce GTX 460/PCI/SSE2 -- 4.2.0. Its more smooth than ANGLE, I am getting 59 to 80 frames with 1000 fish. My build Change set is 9545b88eed82.

You might be interested in bug 618898 which would allow us to default to OpenGL on NVIDIA cards.