2 ms·
> I would think it's ridiculous to expect a thread to be able to grab 100% of the GPU, personally. Folks that spend big bucks on dedicated hardware might disag
by ndesaulniers 11y ago
> I would think it's ridiculous to expect a thread to be able to grab 100% of the GPU, personally.
Folks that spend big bucks on dedicated hardware might disagree.
> If a game isn't fullscreen, I'm not prioritizing its framerate; it should (be forced to) play nice with my desktop.
That's fair. That was also Microsoft's reason for not implementing WebGL for a long time, IIRC. "DoS." Thing is, either you want a thread to take everything (like when you play a game fullscreen), or you can just close a demanding application (or tab on a site with misbehaving/straining WebGL).
- derefr 11y ago"You can just close a demanding application" assumes your system isn't crawling and unresponsive in a way that prevents you from finding the offender, though. As GPUs become increasingly utilized for not-graphics, we'll increasingly see badly-written programs doing synchronous waits on the results of GPGPU calculations, and thus increasingly see GPU hogs stalling the CPU threads (and thus the event loops) of those programs.
- ndesaulniers 11y ago> You can just close a demanding application Sorry, I misspoke. Having a watchdog timer reset the GPU is indeed a useful feature. I meant to say "you can just avoid such a site in the future." See greggman's point #1 on DoS: http://games.greggman.com/game/webgl-security-and-microsoft-bullshit/ http://games.greggman.com/game/webgl-security-and-microsoft-...