Running MiniMax M2.7 on H200
Quick answer
MiniMax M2.7 sustains 2,523 tokens/s per GPU on H200 at 50 tokens/s per user, which works out to $0.13 per million tokens at hyperscaler pricing, served by vLLM. Fastest measured TTFT: 0.1 ms; fastest TPOT: 0.0 ms (each the best across all configs, not one run).
Benchmarked configs
24
Serving engines
vLLM
Precisions
fp8
Run dates
2026-03-28 → 2026-06-05
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 | 3,662 | $0.093 | vLLM | fp8 |
| 50 tok/s | 2,523 | $0.13 | vLLM | fp8 |
| 75 tok/s | 1,767 | $0.19 | vLLM | fp8 |
| 100 tok/s | 1,067 | $0.32 | vLLM | fp8 |
| 150 tok/s | - | - | vLLM | fp8 |
| 200 tok/s | - | - | vLLM | 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 | $1.22 | $0.13 |
| Neocloud | $1.59 | $0.18 |
| Retail | $2.05 | $0.23 |
Frequently asked questions
- How fast is MiniMax M2.7 on H200?
- At an interactivity target of 50 tokens/s per user on a single-turn chat workload (8k input / 1k output), H200 sustains 2,523 tokens/s per GPU serving MiniMax M2.7 with vLLM in FP8. Peak measured throughput across all configs is 6,074 tokens/s per GPU.
- How much does it cost to serve MiniMax M2.7 on H200?
- $0.13 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 MiniMax M2.7 on H200?
- The runs behind this page used vLLM in FP8. Engines are rebuilt and re-benchmarked continuously, so the best config can change between visits.
- How are these MiniMax M2.7 numbers measured?
- Every number is measured on real H200 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-05. The same derivation powers the InferenceX overview leaderboard.