Running DeepSeek R1 on MI355X
Quick answer
DeepSeek R1 sustains 1,608 tokens/s per GPU on MI355X at 50 tokens/s per user, which works out to $0.26 per million tokens at hyperscaler pricing, served by SGLang. Fastest measured TTFT: 0.1 ms; fastest TPOT: 0.0 ms (each the best across all configs, not one run).
Benchmarked configs
307
Serving engines
ATOM¹, MoRI SGLang, SGLang
Precisions
fp4, fp8
Run dates
2026-01-14 → 2026-06-11
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 | 1,134 | $0.37 | MoRI SGLang | fp8 |
| 50 tok/s | 1,608 | $0.26 | SGLang | fp8 |
| 75 tok/s | 4,027 | $0.10 | MoRI SGLang | fp4 |
| 100 tok/s | 3,616 | $0.12 | MoRI SGLang | fp4 |
| 150 tok/s | 1,568 | $0.27 | MoRI SGLang | fp4 |
| 200 tok/s | 413 | $1.01 | MoRI SGLang | fp4 |
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 | $1.50 | $0.26 |
| Neocloud | $2.09 | $0.36 |
| Retail | $2.10 | $0.36 |
Frequently asked questions
- How fast is DeepSeek R1 on MI355X?
- At an interactivity target of 50 tokens/s per user on a single-turn chat workload (8k input / 1k output), MI355X sustains 1,608 tokens/s per GPU serving DeepSeek R1 with SGLang in FP8. Peak measured throughput across all configs is 8,175 tokens/s per GPU.
- How much does it cost to serve DeepSeek R1 on MI355X?
- $0.26 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 MI355X?
- The runs behind this page used ATOM¹, MoRI SGLang, SGLang in FP4, FP8, including disaggregated prefill and multi-node serving. 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 MI355X 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-06-11. The same derivation powers the InferenceX overview leaderboard.