Hacker News new | ask | show | jobs
by mappu 3950 days ago
300 000 sprites, i5 2500, R9 270, Windows 8

- Chrome 44: 60 FPS constant

- Firefox 39: 49 FPS

- Firefox 40: 59-60 FPS

- IE 11: 10-12 FPS, very poor.

The FPS counter doesn't appear on my smartphone (falcon, CM12.1 Browser), but i would estimate the performance is at about 10-15FPS at the default number of sprites, let alone the full 300 000.
1 comments
satori99 3950 days ago
For me, (nVidia GTX 980) Chrome beats Firefox on Windows 8.1 by a lot when rendering 300,000 bunnies.

- Chrome 44: 100 FPS

- Firefox 40: 60 FPS

- IE 11: 10 FPS

I don't think that FF is limiting itself to 60 FPS as I have a 144Hz monitor and other WebGL demos can render at frame rates well in excess of 60 FPS in firefox.

link
ahoge 3950 days ago
Firefox's rAF implementation is currently hardcoded at 60 FPS.

https://bugzilla.mozilla.org/show_bug.cgi?id=707884

link
satori99 3950 days ago
That is odd because the three.js demos i run report well in excess of 60 fps in FF when my monitor refresh rate is set 144Hz. The stats.js component only measures up to 100FPS and the simple demos often exceed that.

edit: I also have G-SYNC enabled and I noticed that the bug thread says the FF syncs to vsync on Windows. nVidia's G-SYNC might be messing with vsync to achieve higher than 60FPS on supported monitors?

link