4 ms·

Seems that screen/window resolution is an important factor.

• fenomas 11y ago
  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)
  • eduardo-costa 11y ago
    Sometime ago I profiled the FPS Stats tool and it generated some DOM garbage!