upvote

points

by Philip-J-Fry15 hours ago |
comments
upvoteby Rohansi14 hours ago|
[-]
> A website shouldn't be pinning CPU or GPU.

That's exactly what I was saying. Rendering a few widgets shouldn't pin your CPU or GPU because it's so little work.

This page, however, has an animated SVG and moving DOM elements in the header which consume far more resources than the widgets it is trying to showcase. Compare usage before and after deleting the header element (`section.hero`) in the inspector to see for yourself.

reply
upvoteby globnomulous13 hours ago|
parent|
[-]
> > A website shouldn't be pinning CPU or GPU.

> That's exactly what I was saying. Rendering a few widgets shouldn't pin your CPU or GPU because it's so little work.

Your comment doesn't say this at all:

> > This is the kind of thing usually a human notices and says 'dont do that, that is kind of crazy'.

> It's not crazy. That is literally what 99.99% of video games do. They repaint everything constantly, only limited by either your vsync rate or hardware.

Am I missing something? Are you referring to some other part of the thread?

reply
upvoteby Rohansi13 hours ago|
parent|
[-]
Sorry, I meant to say that it was what I was suggesting. Video games render a lot more than the widgets on that website. Rendering less takes less time, so your `requestAnimationFrame` loop idles longer between executions waiting for vsync, which means your CPU or GPU usage is not pinned.
reply