ComfyUI's official AMD docs recommend using ROCm 7.2. However, I tested Comfy a month back with the then new ROCm 7.14 on an AMD Strix Halo (see my howto), and it flew (~18-24% faster depending on the model).
Since ROCm 10.0 has been out for a couple of weeks now, I ran the nightly version (10.1.0a20260823) to see if it's any better.
Spoiler: With one exception, the same or slightly faster. In any case, both v7.14 and v10 are significantly faster than v7.2, so upgrade.
¶Why nightly though?
Because the stable ROCm 10.0.x wheels carry the same idle CPU busy-spin bug as 7.14. The fix has landed in AMD's nightly 10.1.0a20260823 build, so nightly it is until a 10.0.x or 10.1.x stable release fixes it in the future.
Now let's set it up.
This guide assumes you are starting from scratch. If you already have ComfyUI set up, skip to creating the venv.
¶Get the appropriate Python version
ComfyUI devs recommend Python 3.12, 3.13 or 3.14 with a disclaimer that some custom nodes might not work properly with Python 3.14.
I use Comfy with Python 3.14 and all of my custom nodes work just fine. If something doesn't work on your system, try Python 3.12 or 3.13.
¶Find your GPU architecture
Run rocm-smi --showproductname, match the GFX Version to the table below, and note it down. You will need this while installing PyTorch:
| GFX target | GPU series |
|---|---|
gfx1201 |
RX 9070 XT, RX 9070 |
gfx1200 |
RX 9060 XT, RX 9060 |
gfx1100 |
RX 7900 XTX, RX 7900 XT |
gfx1101 |
RX 7800 XT, RX 7700 XT |
gfx1102 |
RX 7600 |
gfx1151 |
Ryzen AI Max+ 395, Max 390 (Strix Halo) |
gfx1150 |
Ryzen AI 9 HX 370 (Strix Point) |
gfx942 |
MI300X, MI325X |
¶Install ComfyUI
¶Clone the ComfyUI repo and cd into it
git clone https://github.com/Comfy-Org/ComfyUI
cd ComfyUI
¶Create the venv
Inside the ComfyUI folder, run:
python3 -m venv venv-rocm10
source venv-rocm10/bin/activate
pip install -U pip wheel
If you already have a venv set up, this will create a parallel environment with ROCm 10 PyTorch. This way, you can switch between the two environments if needed.
¶Install ROCm 10 PyTorch
Important: device-gfx1151 will work only with Ryzen AI Max+ 395 / 390 (Strix Halo) systems. Replace it with your GPU's tag.
pip install \
--extra-index-url https://nightly.repo.amd.com/rocm/pytorch/whl-next/ \
--extra-index-url https://nightly.repo.amd.com/rocm/whl-next/ \
"torch[device-gfx1151]==2.13.0+rocm10.1.0a20260823" \
"torchvision[device-gfx1151]==0.28.0+rocm10.1.0a20260823" \
"torchaudio==2.11.0.2+rocm10.1.0a20260823"
The ROCm version is pinned to a known-good nightly build. Feel free to experiment with new nightlies.
¶Install remaining ComfyUI dependencies
pip install -r requirements.txt
pip check
Verify:
python -c "import torch; print(torch.__version__, torch.cuda.is_available(), torch.cuda.get_device_name(0))"
This should print 2.13.0+rocm10.1.0a20260823 True your-GPU-name.
¶Custom nodes
Some custom nodes will probably whine about unmet dependencies. You can go to each node's folder and run pip install -r requirements.txt, or ask your agent to start Comfy using your preferred flags, monitor its output, and install the missing deps for each node.
Tell your agent to make sure torch, torchvision, and torchaudio aren't replaced by Nvidia alternatives during installation, or your setup will break.
¶Run ComfyUI
We're ready to go. Strix Halo and other high-VRAM machines can use the --highvram flag.
python main.py --bf16-vae --disable-mmap --highvram
For other GPUs (or to conserve VRAM on Strix Halo), use these settings (based on community feedback):
python main.py --bf16-vae --disable-mmap --enable-dynamic-vram --disable-pinned-memory --reserve-vram 1.0
¶Switching between ROCm environments
If you have an existing venv (e.g. ROCm 7.14 from my previous guide), you can switch back to it by deactivating the current one and activating the other:
deactivate
source venv-rocm714/bin/activate
LD_PRELOAD="./libhsa_shim.so /lib64/libhsa-runtime64.so.1.18.0" \
python main.py --bf16-vae --disable-mmap --highvram
Now run ComfyUI as usual.
¶Benchmark results
Everything runs on a Strix Halo (Ryzen AI Max+ 395) with the --bf16-vae --disable-mmap --highvram flags. Differences under ~1.5 s are just normal gen-to-gen variations.
gen 1 is from a cold start (freshly started ComfyUI process), while gen 2 is warm (the models already in VRAM), which is why first and second gen times differ.
I also slightly varied the prompt between runs (e.g., different hair/glasses for the image gen models, different color-scheme for the Flux edit model).
| Model | ROCm 7.14 gen 1 / gen 2 | ROCm 10 gen 1 / gen 2 | Verdict |
|---|---|---|---|
| Krea 2 Turbo (1 MP) | 48.8 s / 45.2 s | 48.6 s / 44.4 s | Same (within variation) |
| Krea 2 Turbo (1.4 MP) | 71.0 s / 67.2 s | 66.9 s / 61.9 s | ROCm 10 faster (~6% / ~8%) |
| Anima Aesthetic (1 MP) | 69.3 s / 63.3 s | 63.8 s / 60.4 s | ROCm 10 faster (~8% / ~5%) |
| Anima Aesthetic (1.4 MP) | 114.3 s / 110.4 s | 118.5 s / 115.2 s | ROCm 7.14 faster (~3.5% / 4%) |
| Flux 2 Klein Edit 9B (1 MP input/output) | 47.3 s / 38.9 s | 46.1 s / 37.9 s | Same (within variation) |
| SeedVR2 4k image upscale (1024x1024 source) | 90.6 s | 91.1 s | Same (within variation) |
Basically, ROCm 10 is the same or faster than ROCm 7.14 across the board, except 1.4+ MP images with Anima Aesthetic, which is somewhat slower on ROCm 10.
Weird, but it is what it is.