-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Add support to filter_ep_devices using ep or device metadata in perftest #26255
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
Add support to filter_ep_devices using ep or device metadata in perftest #26255
Conversation
/azp run Linux QNN CI Pipeline,Win_TRT_Minimal_CUDA_Test_CI,Windows ARM64 QNN CI Pipeline,Windows GPU Doc Gen CI Pipeline,Windows x64 QNN CI Pipeline |
Azure Pipelines successfully started running 4 pipeline(s). |
/azp run Linux QNN CI Pipeline,Win_TRT_Minimal_CUDA_Test_CI,Windows ARM64 QNN CI Pipeline,Windows GPU Doc Gen CI Pipeline,Windows x64 QNN CI Pipeline |
Commenter does not have sufficient privileges for PR 26255 in repo microsoft/onnxruntime |
@chilo-ms Can you please re-run the CI ? I pushed a fix for lint error |
/azp run Linux QNN CI Pipeline,Win_TRT_Minimal_CUDA_Test_CI,Windows ARM64 QNN CI Pipeline,Windows GPU Doc Gen CI Pipeline,Windows x64 QNN CI Pipeline |
Azure Pipelines successfully started running 4 pipeline(s). |
Reopen this PR to trigger "license/cla" pipeline |
/azp run Linux QNN CI Pipeline,Win_TRT_Minimal_CUDA_Test_CI,Windows ARM64 QNN CI Pipeline,Windows GPU Doc Gen CI Pipeline,Windows x64 QNN CI Pipeline |
Azure Pipelines successfully started running 4 pipeline(s). |
Please help merge main to include the fix to pass the failing pipelines |
done |
/azp run Linux QNN CI Pipeline,Win_TRT_Minimal_CUDA_Test_CI,Windows ARM64 QNN CI Pipeline,Windows GPU Doc Gen CI Pipeline,Windows x64 QNN CI Pipeline |
Azure Pipelines successfully started running 4 pipeline(s). |
Add support for ep device selection in ORT perf test by filtering the ep device list based on EP or Device metadata
--filter_ep_devices
(Specifies EP or Device metadata entries as key-value pairs to filter ep devices passed to AppendExecutionProvider_V2.[Usage]:
--filter_ep_devices "<key1>|<value1> <key2>|<value2>"
Devices that match any of the key-value pair will be appended to the session. --select_ep_devices will take precedence over this option.
Examples with OpenVINO EP:
--plugin_ep_libs "OpenVINOExecutionProvider|onnxruntime_providers_openvino_plugin.dll" --plugin_eps OpenVINOExecutionProvider --filter_ep_devices "ov_device|NPU"
[Plugin EP] EP Device [Index: 1, Name: OpenVINOExecutionProvider, Type: 2] has been added to session.
--plugin_ep_libs "OpenVINOExecutionProvider|onnxruntime_providers_openvino_plugin.dll" --plugin_eps OpenVINOExecutionProvider.AUTO --filter_ep_devices "ov_device|NPU ov_device|CPU"
[Plugin EP] EP Device [Index: 3, Name: OpenVINOExecutionProvider.AUTO, Type: 2] has been added to session.
[Plugin EP] EP Device [Index: 4, Name: OpenVINOExecutionProvider.AUTO, Type: 0] has been added to session.