Running DeepSeek R1 on MI300X
Quick answer
DeepSeek R1 sustains 240 tokens/s per GPU on MI300X at 50 tokens/s per user, which works out to $1.10 per million tokens at hyperscaler pricing, served by SGLang. Fastest measured TTFT: 0.2 ms; fastest TPOT: 0.0 ms (each the best across all configs, not one run).
Benchmarked configs
15
Serving engines
SGLang
Precisions
fp8
Run dates
2026-02-27 → 2026-05-18
Throughput at every interactivity target
Serving is a trade-off: push more concurrent users through a GPU and each user's tokens arrive slower. The ladder below reads the measured frontier at each per-user speed target on a single-turn chat workload (8k input / 1k output), using the best engine and precision at that point.
| Per-user target | Tokens/s per GPU | $ / 1M tokens | Engine | Precision |
|---|---|---|---|---|
| 30 tok/s | 630 | $0.42 | SGLang | fp8 |
| 50 tok/s | 240 | $1.10 | SGLang | fp8 |
| 75 tok/s | - | - | SGLang | fp8 |
| 100 tok/s | - | - | SGLang | fp8 |
| 150 tok/s | - | - | SGLang | fp8 |
| 200 tok/s | - | - | SGLang | fp8 |
What serving actually costs
Converting the 50 tokens/s per user operating point to $ per million total tokens across rental pricing tiers from the SemiAnalysis AI Cloud TCO model.
| Pricing tier | $ / GPU / hr | $ / 1M tokens |
|---|---|---|
| Hyperscaler | $0.95 | $1.10 |
| Neocloud | $1.16 | $1.34 |
| Retail | $1.30 | $1.50 |
Frequently asked questions
- How fast is DeepSeek R1 on MI300X?
- At an interactivity target of 50 tokens/s per user on a single-turn chat workload (8k input / 1k output), MI300X sustains 240 tokens/s per GPU serving DeepSeek R1 with SGLang in FP8. Peak measured throughput across all configs is 892 tokens/s per GPU.
- How much does it cost to serve DeepSeek R1 on MI300X?
- $1.10 per million total tokens at hyperscaler $/GPU/hr pricing, at 50 tokens/s per user. Neocloud and retail rental tiers are tabulated above; slower interactivity targets lower the cost further.
- Which serving engines run DeepSeek R1 on MI300X?
- The runs behind this page used SGLang in FP8. Engines are rebuilt and re-benchmarked continuously, so the best config can change between visits.
- How are these DeepSeek R1 numbers measured?
- Every number is measured on real MI300X hardware by the InferenceX fleet, sweeping concurrency on a single-turn chat workload (8k input / 1k output) to trace the throughput-versus-interactivity frontier; the newest run landed on 2026-05-18. The same derivation powers the InferenceX overview leaderboard.