-
Notifications
You must be signed in to change notification settings - Fork 761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Enable OpenVINO backend for WASI-NN #1063
Comments
|
Hi ~ @hydai, I am ziyuan Wang, currently study at ZheJiang University and will graduate at June 30th this summer. I would like to apply for LFX mentorship in this year and work on it. First, I have open source experience through last year's internship in AliYun while working with CNCF ToC Zhanglei's Team and I made contribution to oam/KubeVela. Thus, I think I'm fit for this task and I would be grateful if you could guide me to relevant resources. Thanks~ |
|
Hi @wangyuan249, I just updated the Minimum qualifications. If you are interested in this issue, please finish the challenge. It will help you to get familiar with the WasmEdge data structure and how to interact with the WasmEdge. |
|
Hi @hydai, |
Motivation
In the previous ticket #343, we already have some
WASI-NNimplementation. However, the backend is using ONNX. In this ticket, we would like to have both ONNX and OpenVINO backend.Machine Learning is a big topic nowadays. WasmEdge already provides a set of TensorFlow host functions to enable the ML inference in WebAssembly. However, these TensorFlow host functions are defined by us and they are just a Wasm function binding from the TensorFlow C API.
Here comes a standard, the WASI-NN proposal provides a new way to perform neural network inferencing by using a runtime-provided implementation that can leverage host native optimizations, CPU multi-threading, or powerful hardware devices such as GPUs or TPUs.
Specification
WASI-NNcomponent.Minimum qualifications
To apply this LFX mentorship, there are some minimum qualifications:
Appendix
The text was updated successfully, but these errors were encountered: