Closed vladmandic closed 3 years ago
Yes, this change will be out with Chrome 91 release. Please see the official link for how to setup coop and coep: https://web.dev/coop-coep/
Here's some updated progress on this change: https://developer.chrome.com/blog/enabling-shared-array-buffer/
@lina128 What if it is impossible to implement cross-origin isolated pages? Will tensorflow.js wasm backend add an ArrayBuffer
fallback for unavailable SharedArrayBuffer
, to make it less efficient but still workable?
Hi @SukkaW, without cross-origin isolation, the wasm baskend will fallback to simd only (without multi-threading support).
without cross-origin isolation, the wasm baskend will fallback to simd only (without multi-threading support).
Thanks!
Thanks @jinjingforever . Another question is: could cross-origin isolation be enabled for tfjs e2e benchmark site? Otherwise, users can only test it without multi-threading support.
Good point @huningxin! I think the e2e benchmark is hosting on github page which doesn't support custom headers. I will discuss with the team and see where to move it. Thanks!
@huningxin We set up a new benchmark site that has the cross-origin isolation set up: https://tfjs-benchmarks.web.app/local-benchmark/. Thanks!
It works like a charm. Thanks @jinjingforever .
Running
TFJS
3.5.0 withWASM
backend and SIMD & multithreading enabled results in warnings in browser console:Which happens in internal WASM test in
flags_wasm.ts
:Environment: TFJS 3.5.0 with Edge/Chromium 90 on Windows 10 with WASM backend (SIMD and MultiThreading enabled)