Vladimir Mandic
Vladimir Mandic
related #6683
I love this improvement as it results in quite significant performance improvements but at the moment it causes conflict with `@tensorflow/tfjs-backend-wasm` as soon as that module is loaded regardless if...
@gyagp thanks for the explanation tried with chrome canary 106.0.5206.0 - `await tensor.data()` --> average 107ms - `tensor.dataSync()` --> average 99ms difference is definitely smaller, but still noticeable at 10%...
@gyagp after enabling `USE_SETTIMEOUTWPM`, i'm getting errors in `tfjs-backend-wasm-threaded-simd.worker.js` > worker.js received unknown command undefined and i'm clearly not using wasm here at all, its just that my `tfjs` bundle...
@gyagp i've removed `tfjs-backend-wasm` from my `tfjs` bundle and test now runs results show some, but still far from sync data download performance tensor with shape [1, 720, 720, 3],...
@gyagp > but 4ms delay is real and critical for an application that targets 60FPS, or cares about every millisecond very true i've tried `USE_SETTIMEOUTWPM` on a different use-case, an...
as soon as `@tensorflow/tfjs-backend-wasm` is loaded and `USE_SETTIMEOUTCUSTOM` is enabled, there are problems regardless if WASM is used or not as WASM init code happens on module load worker.js received...
@gyagp @shaoboyan i just redid all the tests - seems there is quite a difference depending on: - timings for initial iterations are all over the place, and not just...
@shaoboyan i'm not sure what is the ask - i've already done that - not just *several* warmup rounds, but 100 and then measuring average between rounds 100 to 200....
@gyagp i'm not sure upgrading `emscripten` would solve it as fix solved it for , but it still needs a same fix for -those are two different places in the...