How does TaskQueue/TaskWorklet tie into WASM threads? #9

Activity

1. developit commented on Nov 15, 2018

   

   developit

   on Nov 15, 2018

   Owner

   More actions

   I think right now there isn't really an interaction between the two. The polyfill would allow WASM as it is implemented using Workers for the threadpool, however the proposal (publishing soon) and our experimental implementation in Chromium use a proper Worklet backing in the pool and thus don't allow for WASM usage.
2. chicoxyzzy commented on Nov 16, 2018

   

   chicoxyzzy

   on Nov 16, 2018

   More actions

   It's possible to use WebAssembly in AudioWorklet in stable Chrome so it's confusing that it's not the case for TaskWorklet
3. chicoxyzzy commented on Nov 16, 2018

   

   chicoxyzzy

   on Nov 16, 2018

   More actions

   Basically it should be possible to load js module via Worklet.addModule and load+compile+instantiate wasm in this module
4. chicoxyzzy commented on Nov 19, 2018

   

   chicoxyzzy

   on Nov 19, 2018

   More actions

   Also just found this reference that WebAssembly namespace should be exposed to window, worker and worklet
5. developit commented on Nov 21, 2018

   

   developit

   on Nov 21, 2018

   Owner

   More actions

   @chicoxyzzy you're right, I'm not sure why I implied WASM couldn't be used - there's no reason it can't here.

   const wasm = WebAssembly.instantiateStreaming(fetch('worklet.wasm'));
   
   class WasmDemoProcessor {
     async process(data) {
       const { instance } = await wasm;
       return instance.exports.doThing(data);
     }
   }
   
   registerTask('wasm-demo', WasmDemoProcessor);

   👍React with 👍1Reacted by Sergey Rubanov