microsoft / microsoft/onnxruntime

Get the actual execution device name and vendor information

Open
#16,481 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

ep:OpenVINO feature request
Dominant language
C++
Stars
21.9k
Forks
4.2k
Avg merge
4d 11h
Merged PRs (30d)
184

Description

### Describe the feature request

At the moment it seems that there is no method to get more specific device information except the device type (`CPU, GPU, ...`).

Would it be possible to add something similar to `core.get_property("CPU", ov::device::full_name);` ([OpenVINO](https://docs.openvino.ai/2022.1/openvino_2_0_configure_devices.html)) to onnxruntime? OpenVINO for example returns the following string on my CPU: `11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz`

It could work like the `session.get_provider_options()` but with a new name: `session.get_provider_infos()`.

### Describe scenario use case

For example for error investigation it would be great to know, what kind of hardware was used to infer the model. Also for automatic benchmarking it would be good to be able to store the current hardware name.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the proposed core.get_property("CPU", ov::device::full_name) approach with session.get_provider_options(). Determine how the proposed session.get_provider_infos() API should expose actual execution device names and vendor information across providers. Done means the API and its supported provider coverage are agreed and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.