4 ms·
It's #2. Redrawing at 60hz (or as close as the machine can come) is what hits the cpu so hard.
by hunterloftis 12y ago
It's #2. Redrawing at 60hz (or as close as the machine can come) is what hits the cpu so hard.
- s-macke 12y agoNo, I don't use requestAnimationFrame right now. I think when I wrote it, it was not supported by IE. But can't remember. I calculate as close as the machine can but with a window.setTimeout(Update, 0); in order to be responsive.