Hyperloom compatibility matrix#

2026-08-27

4 min read time

Applies to Linux

This topic lists the hardware, inference frameworks, and container images that Hyperloom is validated against.

Note

ROCm versions or framework builds not listed in this matrix might work, but are not regularly tested.

Hyperloom support matrix#

The following table lists the minimum requirements for running Hyperloom.

Requirement

Support

AMD Instinct™ GPU

MI300X, MI325X, MI355X

Operating System

Ubuntu 22.04, Ubuntu 24.04

ROCm Version

7.2.x

Python

>= 3.10

Inference Framework

SGLang (>= 0.5.12), vLLM (>= 0.21.0), plus custom for your own benchmark script

Kernel Languages

HIP, Triton, FlyDSL

Component support matrix#

The following table lists the validated Hyperloom version and component combinations.

Hyperloom version

Component

GPU

ROCm version

Ubuntu

Python

GitHub

1.0.0

TraceLens 1.0.0

Hardware-agnostic

No dependency

OS-independent

>= 3.6

GEAK 4.0.0

MI300X, MI325X, MI355X

6.4.x, 7.0.x, 7.1.x, 7.2.x, 10.0.0

22.04, 24.04

3.8, 3.12

IntelliKit 0.1.1

MI300X, MI325X, MI355X

7.2.x, 10.0.0

22.04, 24.04

>= 3.10

AgentKernelArena 0.2.0

MI300X, MI325X, MI355X

7.2.x

22.04, 24.04

>= 3.10

Magpie 0.2.0

MI300X, MI325X, MI355X

7.0.x, 7.1.x, 7.2.x, 10.0.0

22.04, 24.04

>= 3.10

Note

TraceLens does not have hard requirements for the GPU, ROCm version, or the OS; it has scripts to verify whether a trace is valid/parseable. TraceLens is:

  • OS-independent and runs anywhere Python does.

  • Not limited to MI300X/MI325X/MI355X; it’s hardware-agnostic.

See the TraceLens documentation for more information.

Note

MI325X shares the gfx942/CDNA3 runner family with MI300X. Hyperloom keeps the resolved GPU types distinct, but Magpie benchmark rendering reuses the MI300X runner scripts and image family unless a dedicated image is supplied.

Inference frameworks#

The following inference frameworks are supported:

Framework

ROCm version

Notes

SGLang

7.2.4

Default framework; recommended docker/bare-metal stack uses rocm724 (see below)

vLLM

7.2.3

Do not mix frameworks within one session

custom

Host-defined

Escape hatch for your own benchmark script; Hyperloom does not manage the server lifecycle. Requires HYPERLOOM_BENCHMARK_BACKEND=bypass plus --framework-path (or FRAMEWORK_REPO_PATH) and --benchmark-scripts-dir (or HYPERLOOM_BYPASS_SCRIPTS_DIR); the CLI exits with status 2 when any of the three is missing.

Container images#

Pick the image that matches your environment. Public Docker Hub refs are used on your own GPU machine: the official upstream lmsysorg/sglang-rocm:<tag> for SGLang and vllm/vllm-openai-rocm:<tag> for vLLM. If your deployment uses a private registry mirror, set the registry prefix accordingly.

Image

GPU

lmsysorg/sglang-rocm:v0.5.17-rocm724-mi30x-20260821

MI300X / MI325X

lmsysorg/sglang-rocm:v0.5.17-rocm724-mi35x-20260821

MI355X

vllm/vllm-openai-rocm:v0.27.1

MI300X / MI325X / MI355X

The vLLM image entrypoint is vllm serve, so override it (for example --entrypoint tail) when starting a long-running Hyperloom container.

Browse all available tags at hub.docker.com/r/lmsysorg/sglang-rocm/tags and hub.docker.com/r/vllm/vllm-openai-rocm/tags.