Recently, I've implemented the Stats.js plugin to keep track of my three.js performance.
Something seems off with the FPS (frames rendered per second) and MS (milliseconds needed to render a frame) information:
According to my calculations, if it takes 4 milliseconds to render a frame, then theoretically I should be able to achieve 1000 milliseconds / 4 milliseconds = 250 frames per second. This is much higher than what RequestAnimationFrame typically provides, but significantly lower than the reported 17 FPS by the stats plugin.
What could be the missing piece in this puzzle?