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?
Show HN: WebGL Sprites Benchmark
21–25 of 25 posts
Re: Show HN: WebGL Sprites Benchmark
#22On 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…
Re: Show HN: WebGL Sprites Benchmark
#23Seems 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)
Re: Show HN: WebGL Sprites Benchmark
#24how do you increase to more than 300K he says to modify the hash but this does not work on my comp
Re: Show HN: WebGL Sprites Benchmark
#25On 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…