[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] PSA: upcoming CPU throttle mechanism to severly limit and cripple graphics and processing intensive web applications

While these CPU throttling proposals could adversely affect WebGL content, this mailing list is not the appropriate place to discuss them. Anyone should feel free to comment on the bug directly.

Please keep the conversations on this list civil and professional. The follow-ups to this email were not. I don't want to have to introduce moderation on this list.



On Thu, Oct 19, 2017 at 2:12 PM, Florian Bösch <pyalot@gmail.com> wrote:
Ojan Vafai of the chrome engineering team lays out plans to limit CPU use by websites.

If a site is using more than XX% CPU for more than YY seconds, then we put the page into "battery saver mode" where we aggressively throttle tasks and show a toast [notification popup] allowing the user to opt-out of battery saver mode. When a battery saver mode tab is backgrounded, we stop running tasks entirely.

This will impact many things such as:
  • graphics intensive code
  • physics simulation
  • collision detection
  • scientific simulations
  • 3d file format conversion
  • data processing
  • etc.
Another whole array of use-cases gone from the web. Good job.