MiniMax M3 428BNVIDIA Hopper
Running MiniMax M3 on H200
Quick answer
MiniMax M3 runs on H200: 113 benchmarked configs so far. See the interactivity ladder below for measured operating points.
Benchmarked configs
113
Serving engines
vLLM
Precisions
fp8
Run dates
2026-06-13 → 2026-09-15
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 the AgentX agentic coding workload, using the best engine and precision at that point.
| Per-user target | Tokens/s per GPU | $ / 1M tokens | Engine | Precision |
|---|---|---|---|---|
| 30 tok/s | - | - | vLLM | fp8 |
| 50 tok/s | - | - | vLLM | fp8 |
| 75 tok/s | 6,599 | $0.051 | vLLM | fp8 |
| 100 tok/s | 5,758 | $0.059 | vLLM | fp8 |
| 150 tok/s | 3,920 | $0.086 | vLLM | fp8 |
| 200 tok/s | 2,400 | $0.14 | vLLM | fp8 |
Frequently asked questions
- How fast is MiniMax M3 on H200?
- The InferenceX fleet has 113 benchmarked configs for this pairing; see the interactivity ladder above for the operating points reached so far.
- How much does it cost to serve MiniMax M3 on H200?
- Cost per million tokens is derived from measured throughput and $/GPU/hr rates from the SemiAnalysis AI Cloud TCO model; it appears once this pairing reaches the primary interactivity tier.
- Which serving engines run MiniMax M3 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 M3 numbers measured?
- Every number is measured on real H200 hardware by the InferenceX fleet, sweeping concurrency on the AgentX agentic coding workload to trace the throughput-versus-interactivity frontier; the newest run landed on 2026-09-15. The same derivation powers the InferenceX overview leaderboard.