-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
OpenVINO Backend 2022.3 support #5343
Comments
Any updates about this issue? |
@tanmayv25 can you estimate this effort? |
The standalone openvino version in OV backend is dependent upon the version of openvino released in onnxruntime version being shipped with Triton. See here for more information: https://github.com/triton-inference-server/server/blob/main/build.py#L64-L67 The actual update is not expected to be a lot of work. |
@tanmayv25 Hello, Could you please let me know when it will be implemented |
@pranavsharma Does the latest onnxruntime release in Triton ORT v1.14.1 support openvio 2022.3 ? If yes, then we can try upgrading the openvino version in Triton. |
yes. https://onnxruntime.ai/docs/execution-providers/OpenVINO-ExecutionProvider.html#requirements |
We also need the 2022.3 version of openvino_backend, and hope that the official version can be implemented as soon as possible, thank you very much! |
CC: @nnshah1 |
It would be great to see this feature in the future releases. |
The latest version of ORT uses 2023. Does that work? See https://onnxruntime.ai/docs/execution-providers/OpenVINO-ExecutionProvider.html#requirements |
@pranavsharma it supports OpenVINO 2023, but uses the one that is installed in triton server |
Quick update - the team is currently investigating the upgrade. |
@kthui Thanks! ❤️❤️❤️ |
Hello,
Currently triton-inference-server/openvino_backend is based on OpenVINO 2022.01
When will official Triton Container support 2022.3 or later OV backend?
Based on Changelog (2022.02, 2022.03) I assume that update won't cause any issues
Thanks!
The text was updated successfully, but these errors were encountered: