- From: Rafael Cintron <notifications@github.com>
- Date: Sun, 26 May 2024 16:13:22 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 26 May 2024 23:13:26 UTC
@matatk and @cynthia with Chromium on Windows, the WebNN context runs on a separate command queue from the Chromium compositor. Depending on the device, the ML work may run on a separate chip than the one which performs 3D work. Even when it runs on the same chip, the ML work is multi-tasked with other work on the system. As with other web platform features (WebGL, WebGPU, 2D Canvas, CSS blurs, etc) overtaxing the system will eventually affect `requestAnimationFrame`. Web developers need to be responsible with the content they build. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/933#issuecomment-2132427363 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/933/2132427363@github.com>
Received on Sunday, 26 May 2024 23:13:26 UTC