llamaperf

AMD Instinct MI300X 192GB

AMD · 192GB · 3 reports

On the AMD Instinct MI300X 192GB, Qwen3-Coder 30B · 3B active at 16-bit, the model most run on it, generates a median of 184.5 tokens per second from 2 plain runs (community reports, as of 30 Oct 2026).

As of 30 Oct 2026, the models most run on the AMD Instinct MI300X 192GB, with generation and prompt-processing medians from plain runs (one device, one request, no speculative decoding):

Engines people use on it: SGLang 1 (reports) · vLLM 1 (reports)

Run models on your AMD Instinct MI300X 192GB? Add your numbers.

Your coding agent can run a speed test on your machine and send it here with a free account. Or paste a result you've already posted.

Reported performance on the AMD Instinct MI300X 192GB

These reports mix GPU counts and memory setups, so a model listed here may have needed extra cards or CPU offloading. The calculator estimates which models fit in 192 GB of VRAM.

Tone: positiveAMD hardware
generation:
173.0 tokens/s
quant:
BF16 (safetensors)

Reported by the source; GPU count, offloading and concurrent requests can change these figures. Prompt-processing speed is shown only when the source reports it; generation speed cannot tell us time to first token. Check the full setup before comparing.

coding

User benchmarks Qwen3-Coder-30B-A3B in BF16 on a single MI300X 192GB, reporting 173 tok/s decode on a 32K prompt with SGLang defaults. Setup is SGLang 0.5.21 with a 131K context window, prefix caching off, and 256-token replies; vLLM 0.29.1 with AITER attention reached 164 tok/s and llama.cpp (HIP) 108 tok/s with a 20.5 s first token. SGLang was fastest from 1 to 64 users; vLLM only pulled ahead at 128 users. Prefix caching was the only tuning knob that helped, adding 8 to 11 percent. The user notes vLLM without AITER attention collapsed to 27 tok/s total on 16 users with 32K prompts versus 133 on SGLang.

Oct 16, 2026
AMD hardware
generation:
196.0 tokens/s
quant:
BF16 (safetensors)

Reported by the source; GPU count, offloading and concurrent requests can change these figures. Prompt-processing speed is shown only when the source reports it; generation speed cannot tell us time to first token. Check the full setup before comparing.

coding

User benchmarks Qwen3-Coder-30B-A3B-Instruct in BF16 and FP8 on a single MI300X 192GB, reporting 196 tok/s at 1 concurrent request for BF16 and 136 tok/s for FP8. Setup is vLLM 0.29.1 in the rocm/vllm container on AMD Developer Cloud, 1024 prompt tokens and 256 output tokens, vllm bench serve. The 1-request figures are medians of 3 warm runs. FP8 is 31% slower at 1 request but 35% faster at 64 concurrent (3442 vs 2555 tok/s). Accuracy on GSM8K (250 problems) was 96.4% BF16 vs 94.0% FP8. llama.cpp with Q4_K_M reached 187 tok/s at 1 user. Also ran gpt-oss-120b (72 tok/s at 1, 1423 at 64) and Qwen2.5-72B BF16 (26 tok/s at 1, 421 at 32). Total cost about $5.73.

Oct 12, 2026

Qwen3.8 27B

AMD Instinct MI300X 192GB · SGLang · 1,000,000 ctx

Tone: positiveAMD hardware

User reports Qwen3.8-27B at 495 t/s on a single MI300X at 1M context, up from 311 t/s. Setup is dstack's toolkit with source-level patches to SGLang's AITER attention backend. The figure is for four concurrent users at 10k in / 1.5k out, with p50 TTFT under 1.5s.

Sep 7, 2026

Get a weekly email of new AMD Instinct MI300X 192GB reports and newly released models that fit it.

Email me new reports

Reported configurations

Individual observations from this page, not expected speeds or a ranking. Select a model to open its report, with the source and offloading conditions. Reported context may be a limit rather than actual input length.

Model / hardwareQuant / engineReported contextGeneration
Qwen3-Coder 30B (3B active)
AMD Instinct MI300X 192GB
BF16
SGLang
131,072173.0 tokens/s
Qwen3-Coder 30B (3B active)
AMD Instinct MI300X 192GB
BF16
vLLM
Not reported196.0 tokens/s

Frequently asked

How fast is the AMD Instinct MI300X 192GB for local LLMs?

On the AMD Instinct MI300X 192GB, Qwen3-Coder 30B · 3B active at 16-bit, the model most run on it, generates a median of 184.5 tokens per second from 2 plain runs (community reports, as of 30 Oct 2026).