---
title: Execution providers
description: Learn how to enable execution providers to leverage hardware acceleration.
---

import { Callout, Tabs } from 'nextra/components';

Execution providers (EPs) enable ONNX Runtime to execute ONNX graphs with hardware acceleration. If you have specialized hardware like a GPU or NPU, execution providers can provide a massive performance boost to your `ort` applications. For more information on the intricacies of execution providers, see the [ONNX Runtime docs](https://onnxruntime.ai/docs/execution-providers/).

ONNX Runtime must be compiled with support for each execution provider. pyke provides precompiled binaries for some of the most common EPs, so you won't need to compile ONNX Runtime from source. Below is a table showing available EPs, their support in `ort`, and their binary availability status.

* ✅ - Static binaries provided by pyke.
* 🟢 - Dynamic binaries provided by pyke.

| EP | Supported | Binaries |
|:-------- |:------- |:------ |
| [NVIDIA CUDA](https://onnxruntime.ai/docs/execution-providers/CUDA-ExecutionProvider.html) | 🟢 | 🟢 |
| [NVIDIA TensorRT](https://onnxruntime.ai/docs/execution-providers/TensorRT-ExecutionProvider.html) | 🟢 | 🟢 |
| [Microsoft DirectML](https://onnxruntime.ai/docs/execution-providers/DirectML-ExecutionProvider.html) | 🟢 | ✅ |
| [Apple CoreML](https://onnxruntime.ai/docs/execution-providers/CoreML-ExecutionProvider.html) | 🟢 | ✅ |
| [AMD ROCm](https://onnxruntime.ai/docs/execution-providers/ROCm-ExecutionProvider.html) | 🟢 | ❌ |
| [Intel OpenVINO](https://onnxruntime.ai/docs/execution-providers/OpenVINO-ExecutionProvider.html) | 🟢 | ❌ |
| [Intel oneDNN](https://onnxruntime.ai/docs/execution-providers/oneDNN-ExecutionProvider.html) | 🟢 | ❌ |
| [XNNPACK](https://onnxruntime.ai/docs/execution-providers/Xnnpack-ExecutionProvider.html) | 🟢 | ✅ |
| [Qualcomm QNN](https://onnxruntime.ai/docs/execution-providers/QNN-ExecutionProvider.html) | 🟢 | ❌ |
| [Huawei CANN](https://onnxruntime.ai/docs/execution-providers/community-maintained/CANN-ExecutionProvider.html) | 🟢 | ❌ |
| [Android NNAPI](https://onnxruntime.ai/docs/execution-providers/NNAPI-ExecutionProvider.html) | 🟢 | ❌ |
| [Apache TVM](https://onnxruntime.ai/docs/execution-providers/community-maintained/TVM-ExecutionProvider.html) | 🟢 | ❌ |
| [Arm ACL](https://onnxruntime.ai/docs/execution-providers/community-maintained/ACL-ExecutionProvider.html) | 🟢 | ❌ |
| [ArmNN](https://onnxruntime.ai/docs/execution-providers/community-maintained/ArmNN-ExecutionProvider.html) | 🟢 | ❌ |
| [AMD MIGraphX](https://onnxruntime.ai/docs/execution-providers/MIGraphX-ExecutionProvider.html) | 🟢 | ❌ |
| [AMD Vitis AI](https://onnxruntime.ai/docs/execution-providers/Vitis-AI-ExecutionProvider.html) | 🟢 | ❌ |
| [Rockchip RKNPU](https://onnxruntime.ai/docs/execution-providers/community-maintained/RKNPU-ExecutionProvider.html) | 🟢 | ❌ |
| [Microsoft Azure](https://onnxruntime.ai/docs/execution-providers/Azure-ExecutionProvider.html) | ❌ | ❌ |

<Callout type='default'>
    Note that a few execution providers (notably CUDA, TensorRT, and ROCm) are only available with **dynamic linking**. Dynamic linking may require additional setup to get working; see [Linking > Dynamic linking](/setup/linking#dynamic-linking).
</Callout>

## Registering execution providers
<Callout type='info'>
    To use an execution provider with `ort`, you'll need to enable its respective Cargo feature, e.g. the `cuda` feature to use CUDA, or the `coreml` feature to use CoreML.

    ```toml Cargo.toml
    [dependencies]
    ort = { version = "2.0", features = [ "cuda" ] }
    ```

    See [Cargo features](/setup/cargo-features) for the full list of features.
</Callout>

In order to configure sessions to use certain execution providers, you must **register** them when creating an environment or session. You can do this via the `SessionBuilder::with_execution_providers` method. For example, to register the CUDA execution provider for a session:

```rust
use ort::{CUDAExecutionProvider, Session};

fn main() -> anyhow::Result<()> {
    let session = Session::builder()?
        .with_execution_providers([CUDAExecutionProvider::default().build()])?
        .commit_from_file("model.onnx")?;

    Ok(())
}
```

You can, of course, specify multiple execution providers. `ort` will register all EPs specified, in order. If an EP does not support a certain operator in a graph, it will fall back to the next successfully registered EP, or to the CPU if all else fails.

```rust
use ort::{CoreMLExecutionProvider, CUDAExecutionProvider, DirectMLExecutionProvider, TensorRTExecutionProvider, Session};

fn main() -> anyhow::Result<()> {
    let session = Session::builder()?
        .with_execution_providers([
            // Prefer TensorRT over CUDA.
            TensorRTExecutionProvider::default().build(),
            CUDAExecutionProvider::default().build(),
            // Use DirectML on Windows if NVIDIA EPs are not available
            DirectMLExecutionProvider::default().build(),
            // Or use ANE on Apple platforms
            CoreMLExecutionProvider::default().build()
        ])?
        .commit_from_file("model.onnx")?;

    Ok(())
}
```

## Configuring EPs
EPs have configuration options to control behavior or increase performance. Each `XXXExecutionProvider` struct returns a builder with configuration methods. See the [API reference](https://docs.rs/ort/2.0.0-rc.7/ort/index.html?search=ExecutionProvider) for the EP structs for more information on which options are supported and what they do.

```rust
use ort::{CoreMLExecutionProvider, Session};

fn main() -> anyhow::Result<()> {
    let session = Session::builder()?
        .with_execution_providers([
            CoreMLExecutionProvider::default()
                // this model uses control flow operators, so enable CoreML on subgraphs too
                .with_subgraphs()
                // only use the ANE as the CoreML CPU implementation is super slow for this model
                .with_ane_only()
                .build()
        ])?
        .commit_from_file("model.onnx")?;

    Ok(())
}
```

## Fallback behavior
`ort` will silently fail and fall back to executing on the CPU if all execution providers fail to register. In many cases, though, you'll want to show the user an error message when an EP fails to register, or outright abort the process.

You can configure an EP to return an error on failure by adding `.error_on_failure()` after you `.build()` it. In this example, if CUDA doesn't register successfully, the program will exit with an error at `with_execution_providers`:
```rust
use ort::{CoreMLExecutionProvider, Session};

fn main() -> anyhow::Result<()> {
    let session = Session::builder()?
        .with_execution_providers([
            CUDAExecutionProvider::default().build().error_on_failure()
        ])?
        .commit_from_file("model.onnx")?;

    Ok(())
}
```

If you require more complex error handling, you can also manually register execution providers via the `ExecutionProvider::register` method:

```rust
use ort::{CUDAExecutionProvider, ExecutionProvider, Session};

fn main() -> anyhow::Result<()> {
    let builder = Session::builder()?;

    let cuda = CUDAExecutionProvider::default();
    if cuda.register(&builder).is_err() {
        eprintln!("Failed to register CUDA!");
        std::process::exit(1);
    }

    let session = builder.commit_from_file("model.onnx")?;

    Ok(())
}
```

You can also check whether ONNX Runtime is even compiled with support for the execution provider with the `is_available` method.

```rust
use ort::{CoreMLExecutionProvider, ExecutionProvider, Session};

fn main() -> anyhow::Result<()> {
    let builder = Session::builder()?;

    let coreml = CoreMLExecutionProvider::default();
    if !coreml.is_available() {
        eprintln!("Please compile ONNX Runtime with CoreML!");
        std::process::exit(1);
    }

    // Note that even though ONNX Runtime was compiled with CoreML, registration could still fail!
    coreml.register(&builder)?;

    let session = builder.commit_from_file("model.onnx")?;

    Ok(())
}
```

## Global defaults
You can configure `ort` to attempt to register a list of execution providers for all sessions created in an environment.

```rust
use ort::{CUDAExecutionProvider, Session};

fn main() -> anyhow::Result<()> {
    ort::init()
        .with_execution_providers([CUDAExecutionProvider::default().build()])
        .commit()?;

    let session = Session::builder()?.commit_from_file("model.onnx")?;
    // The session will attempt to register the CUDA EP
    // since we configured the environment default.

    Ok(())
}
```

<Callout type='warning'>
    `ort::init` must come before you create any sessions, otherwise the configuration will not take effect!
</Callout>

Sessions configured with their own execution providers will *extend* the execution provider defaults, rather than overriding them.

## Troubleshooting
If it seems like the execution provider is not registering properly, or you are not getting acceptable performance, see the [Troubleshooting: Performance](/troubleshooting/performance) page for more information on how to debug any EP issues.

## Notes

### CUDA
`ort` provides binaries for CUDA 12 with cuDNN 9.x only. Make sure the correct version of CUDA & cuDNN are installed and available on the `PATH`.

### CoreML
Statically linking to CoreML (the default behavior when using downloaded binaries + the `coreml` Cargo feature) requires an additional Rust flag in order to link properly. You'll need to provide the flag `-C link-arg=-fapple-link-rtlib` to `rustc`. You can do this via a build script, an entry in [`.cargo/config.toml`](https://doc.rust-lang.org/cargo/reference/config.html), or an environment variable.

<Tabs items={['Build script', 'Cargo config', 'Environment variable']}>
    <Tabs.Tab title="Build script">
        Add the following to the `build.rs` script of any **binary** crate that uses `ort`.

        ```rust filename="build.rs" copy
        fn main() {
	        #[cfg(any(target_os = "macos", target_os = "ios", target_os = "tvos"))]
            println!("cargo:rustc-link-arg=-fapple-link-rtlib");
        }
        ```

        Library crates do not need this flag, and the usage of it in a library crate will not transitively apply to any binary crates dependent on it.
    </Tabs.Tab>
    <Tabs.Tab title="Cargo config">
        See [Configuration: Hierarchical structure](https://doc.rust-lang.org/cargo/reference/config.html#hierarchical-structure) for more information on where the configuration file can be placed.

        ```toml filename=".cargo/config.toml" copy
        [target.aarch64-apple-darwin]
        rustflags = ["-Clink-arg=-fapple-link-rtlib"]

        [target.x86_64-apple-darwin]
        rustflags = ["-Clink-arg=-fapple-link-rtlib"]
        ```
    </Tabs.Tab>
    <Tabs.Tab title="Environment variable">
        ```shell copy
        $ RUSTFLAGS="-Clink-arg=-fapple-link-rtlib" cargo build
        ```
    </Tabs.Tab>
</Tabs>
