Live data from Hacker News

Show HN: WebGL Sprites Benchmark

haxor.xyz

21–25 of 25 posts

Re: Show HN: WebGL Sprites Benchmark

#21
post #11

FF 40.0.0.3 22-23fps 23fps FF nightly 2015-08-31 24fps chrome 44.0.2403.157 (64bit) 26fps MS Edge 20.10240.16384.0 30-33fps (i7-4770k igfx) The differences weren't visually very apparent. None of the browsers seemed to have periodic GC lag, which in the past certainly was an issue. I'm curious: which browser did you develop this with/optimize on?

Chrome 44. The trick is to create 1 Mesh with 300.000 or more planes and render all stuff once. I pass the x,y data to a texture and sample it in the shader.

Re: Show HN: WebGL Sprites Benchmark

#22

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 someho…

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/

Re: Show HN: WebGL Sprites Benchmark

#23
post #18
post #16

Seems that screen/window resolution is an important factor.

I think it's meant to be a stress test of their particular way of rendering Haxe sprites, not a measure of WebGL or browser performance. It also seems ripe for tuning; it appears to leak a dom object every frame and churn through memory at a pretty epic rate :) (at least per chrome dev tools)

Sometime ago I profiled the FPS Stats tool and it generated some DOM garbage!

Re: Show HN: WebGL Sprites Benchmark

#25

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 someho…

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.
Post reply on HN