For me it showed 400 fps in the top left corner and my laptop fans spun up immediately as well. Seems to render frames continuously rather than waiting for the screen to refresh. Would probably be much less load when limited to 60 fps.
replyYou need to click the "fps" text for it to actually show the FPS value (it'll be green). The 400 you saw was something else.
replyIf you right click on the page, you can 'open image in new tab' and get an image of the current screen. I assume that means it is rendering an entirely new image each frame... which is a tad wild.
reply> I assume that means it is rendering an entirely new image each frame... which is a tad wild.
replyWhat's wild about that? That's exactly what it's doing and what most uses of canvas/WebGL do.
It's wild if it's running at 400 fps because nobody has a screen that refreshes at 400Hz. Every frame rendered past the screen refresh rate is wasted compute. Easily solved by limiting the frame rate.
replyIt's not running at 400 fps, the UI has the current global listener count next to a button that says "fps". The fps is only shown once you click that button. Weird design, I know.
reply