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
For WebNN use case, we need OpenVINO EP to select execution precision on GPU device by respecting the model data types. Say if an operator in the model operates on FP32 tensor, execute it in FP32 precision, if an operator operates on FP16 tensor, execute it in FP16 precision.
Internally, regarding to ACCURACY option, BasicBackend::PopulateConfigValue() sets OpenVINO ov::hint::inference_precision to ov::element::undefined and set execution_mode to ov::hint::execution_mode::ExecutionMode::ACCURACY that works for us.
Describe the issue
There is a regression caused by https://github.com/microsoft/onnxruntime/blob/main/onnxruntime/core/providers/openvino/openvino_provider_factory.cc#L109 from this PR: #23553. Now users can't set "ACCURACY" precision for OV GPU device, it will be overridden as "FP32" which is not as expected. "ACCURACY" precision is really useful, see details: https://docs.openvino.ai/2025/openvino-workflow/running-inference/optimize-inference/precision-control.html#execution-mode, it's not equal to "FP32".
To reproduce
You can set "precision" as "ACCURACY" but it will behavior as "FP32", like https://onnxruntime.ai/docs/execution-providers/OpenVINO-ExecutionProvider.html#cc-api-20:
Urgency
Very urgent, it impacts my performance testing
Platform
Windows
OS Version
win11
ONNX Runtime Installation
Built from Source
ONNX Runtime Version or Commit ID
30c6825
ONNX Runtime API
C++
Architecture
X64
Execution Provider
OpenVINO
Execution Provider Library Version
ov 2024.6
The text was updated successfully, but these errors were encountered: