4 ms·

There's a lot of frames where you are not doing anything, so the image doesn't need to be updated, unlike most games where you always need to be refreshing the

by slx26 6y ago

There's a lot of frames where you are not doing anything, so the image doesn't need to be updated, unlike most games where you always need to be refreshing the screen. Also, I believe that power management for webGL in general is/was quite bad. If I recall correctly, it didn't automatically adapt GPU power usage to the application, but rather it ran on a fixed power level. Maybe I'm wrong or misremembering, though; it would be great if someone else with more knowledge on the topic can give more details.

moron4hire 6y ago
The biggest issue is that a lot of GPUs are blacklisted by browser vendors to force software rendering due to bugs in the GPU drivers that might cause security or overall software reliability issues. And a lot of those GPUs are AMD GPUs. And a lot of those AMD GPUs are in MacBooks. Thus why a lot of MacBook users complain about WebGL stuff pegging their CPU and kicking in the fans.
- Deukhoofd 6y ago
  Do you have a source for that? (And maybe a list of GPUs that are blacklisted as well, so I know what to look out for with some customers?)
  - slx26 6y ago
    Interesting. Found this on a quick search: https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists And the more detailed list for firefox (though only NVIDIA and Intel GPUs on MacOS are reported to be disabled for security issues): https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drive...
    - moron4hire 6y ago
      For the first link > This page was last edited on 3 June 2015 For the second link > This page was last modified on 9 March 2016 There's no way that I'm aware of to find the complete black/whitelists of each browser. The only way I've been able to figure it out before is to disable the blacklisting and see how performance in a WebGL app fairs.

by slx26 6y ago

moron4hire 6y ago

The biggest issue is that a lot of GPUs are blacklisted by browser vendors to force software rendering due to bugs in the GPU drivers that might cause security or overall software reliability issues. And a lot of those GPUs are AMD GPUs. And a lot of those AMD GPUs are in MacBooks. Thus why a lot of MacBook users complain about WebGL stuff pegging their CPU and kicking in the fans.

Deukhoofd 6y ago
Do you have a source for that? (And maybe a list of GPUs that are blacklisted as well, so I know what to look out for with some customers?)
- slx26 6y ago
  Interesting. Found this on a quick search: https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists https://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists And the more detailed list for firefox (though only NVIDIA and Intel GPUs on MacOS are reported to be disabled for security issues): https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drive...
  - moron4hire 6y ago
    For the first link > This page was last edited on 3 June 2015 For the second link > This page was last modified on 9 March 2016 There's no way that I'm aware of to find the complete black/whitelists of each browser. The only way I've been able to figure it out before is to disable the blacklisting and see how performance in a WebGL app fairs.