[FunLover]

On my Mint Desktop:

    Firefox 40.0: 1000 Bunnies at 12 FPS
    Firefox 40.0: 10000 Bunnies at 12 FPS
    Firefox 40.0: 20000 Bunnies at 12 FPS
    Firefox 40.0: 30000 Bunnies at 12 FPS
    
    Chrome 44.0: 1000 Bunnies at 60 FPS
    Chrome 44.0: 10000 Bunnies at 60 FPS
    Chrome 44.0: 30000 Bunnies at 30 FPS

Why this extreme difference between Chrome and Firefox?

about:config in Firefox says "GPU Accelerated Windows: 0/3" so I guess it is somehow not using the GPU. Although then Im surprised it can render 30k bunnies at 12 FPS. On the other hand, it says "WebGL Renderer: NVIDIA Corporation -- GeForce GT 630/PCIe/SSE2". So I guess it's using the GPU. Also I would expect this WebGL demo to not even run without FF using the GPU. Strange. Any ideas?

[fulafel]

https://bugzilla.mozilla.org/show_bug.cgi?id=751082 -> https://bugzilla.mozilla.org/show_bug.cgi?id=594876 & https://bugzilla.mozilla.org/show_bug.cgi?id=942302

The issue seems to be in some kind of limbo, with many users reporting that the compositing mode doesn't even make a difference.

[irq-1]

On Windows both Firefox and Chrome use ANGLE [0] to translate WebGL into DirectX calls, so this will be an issue in the browser not the driver or hardware.

[0] https://code.google.com/p/angleproject/

[TD-Linux]

The bunnies are being rendered on your GPU, but the final frames are being slowly composited in software. There is no fast path to quickly composite WebGL output on Linux yet.