You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the library only operates with the WASM backend even in nodejs. However the better approach should be use node bindings in node and add the webgl EP to automatically fallback to wasm if webgl is not supported by the model.
Hi! Yes, please do make a PR :) any contributions are most welcome.
I just had a question about webgl support for some of the models. When initially testing with the webgl backend, I kept getting errors saying that certain operations weren't supported. It might have been because the models are quantised (8-bit), but either way, I wasn't able to get it working reliably enough.
Hi! Yes, please do make a PR :) any contributions are most welcome.
Good! Let's do it!
Do you have any suggestions?
m open sourcing a project called aiui that transforms a model into an app, My first support was ONNX and it also happened to me. Not every layer is supported in webgl. It will depend on the model, but at least for the supported ones the speed will be very good.
Currently the library only operates with the WASM backend even in nodejs. However the better approach should be use node bindings in node and add the
webgl
EP to automatically fallback towasm
ifwebgl
is not supported by the model.Currenly in code:
Hack to at least improve in the web
I can prepare a PR to improve the execution in node and web 😃
The text was updated successfully, but these errors were encountered: