Skip to content
Discussion options

You must be logged in to vote

Dimitris (@kar-dim) Good question, and the analogy is not quite one-to-one.

Per Microsoft's docs, AMDGPUExecutionProvider "can select an AMD acceleration backend based on the available hardware and workload" — so it is a provider that picks a backend, not one fixed compute backend the way CUDA is. MIGraphX was the graph-compilation/optimization layer (the TensorRT analogue in your comparison), and AMD is folding that capability into the AMDGPU EP path rather than keeping MIGraphX as a standalone EP you select. It is not a ROCm backend — ROCm is AMD's Linux compute stack; on Windows the EP ships as an on-demand download via the ExecutionProviderCatalog APIs.

For standard ONNX inference on …

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
1 reply
@kar-dim
Comment options

Comment options

You must be logged in to vote
1 reply
@kar-dim
Comment options

Answer selected by kar-dim
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
EP Q&A
Labels
None yet
2 participants