MiniMax M3 428B — H100 vs H200
Head-to-head AI inference benchmark comparison of H100 (NVIDIA Hopper) and H200 (NVIDIA Hopper) on MiniMax M3 428B. Latency, throughput, and cost across LLM workloads. Use the chart controls below to switch sequences, precisions, and metrics — same interactions as the main inference chart.
AgentX replays real coding-agent sessions rather than fixed-length prompts, so context grows turn over turn and most of each request is served from cache instead of being recomputed. That turns the comparison into a systems question: KV transfer between nodes, prefix-aware routing, and cache capacity all move the curve alongside raw chip throughput. Fixed-sequence workloads stay the clean baseline for kernel and silicon performance, so the two scenarios answer different questions about the same hardware. Learn more about AgentX →
H100 / H200 on MiniMax M3 428B at 18 tok/s/user: 568 / 4467 tok/s/chip, $0.57 / $0.08 per million tokens. H200 is 654% cheaper per token; H200 delivers 686% more tok/s/chip.
Around the middle of the 7–54 tok/s/user interactivity band, at 30 tok/s/user on MiniMax M3 428B: H100 runs 568 tok/s/chip at $0.57/M tokens, H200 runs 2793 at $0.12/M. H200 is 371% cheaper per token; H200 delivers 391% more tok/s/chip.
Setting 42 tok/s/user as the target on MiniMax M3 428B, H100 produces 568 tok/s/chip ($0.57 per million tokens) and H200 produces 1425 ($0.24). H200 is 140% cheaper per token; H200 delivers 151% more tok/s/chip. (Numbers reflect the default agentic-traces · fp8 selection for this URL — table and chart below update if you change sequence, precision, or model in the controls.)
| Metric | Interactivity (tok/s/user) | Interactivity (tok/s/user) | Interactivity (tok/s/user) |
|---|---|---|---|
| Throughput (tok/s/chip) | H100:568.3H200:4466.6 | H100:568.3H200:2793.0 | H100:568.3H200:1424.7 |
| Cost ($/M tok) | H100:$0.572H200:$0.076 | H100:$0.572H200:$0.121 | H100:$0.572H200:$0.238 |
| tok/s/MW | H100:414826H200:3260320 | H100:414826H200:2038706 | H100:414826H200:1039905 |
| Concurrency | H100:~1H200:~14 | H100:~1H200:~7 | H100:~1H200:~3 |
Total Tokens per $1 USD (Owning - Neocloud Giant) vs. Interactivity
MiniMax M3 428B • FP4 • 8K / 1K • Source: SemiAnalysis InferenceX™
TCO $/chip/hr: VR200: 3.61H100: 1.55H200: 1.59B200: 2.07B300: 2.52GB200: 2.26GB300: 2.79MI300X: 1.16MI325X: 1.32MI355X: 2.09RTX6000PRO: 0.75Jalapeño (Teacup): 1.56
Source: SemiAnalysis Market July 2026 Pricing Surveys & AI Cloud TCO Model
Note: Disaggregated inference configurations (e.g., MoRI SGLang, Dynamo TRTLLM) calculate cost per million tokens per decode chip or per prefill chip, rather than per total chip count. This makes direct token cost comparison with aggregated configs not an apples-to-apples comparison.
Note: Disaggregated inference configurations (e.g., MoRI SGLang, Dynamo TRTLLM) calculate input throughput per decode chip or per prefill chip, rather than per total chip count. This makes direct input throughput comparison with aggregated configs not an apples-to-apples comparison.
Note: Disaggregated inference configurations (e.g., MoRI SGLang, Dynamo TRTLLM) calculate output throughput per decode chip or per prefill chip, rather than per total chip count. This makes direct output throughput comparison with aggregated configs not an apples-to-apples comparison.
Note: Disaggregated inference configurations (e.g., MoRI SGLang, Dynamo TRTLLM) calculate power per decode chip or per prefill chip, rather than per total chip count. This makes direct power comparison with aggregated configs not an apples-to-apples comparison.
Note: Disaggregated inference configurations (e.g., MoRI SGLang, Dynamo TRTLLM) calculate Joules per decode chip or per prefill chip, rather than per total chip count. This makes direct Joules per token comparison with aggregated configs not an apples-to-apples comparison.
No data available
Please change the model, sequence, precision, date range or chip selection.
Shift+Scroll to zoom • Drag to pan • Double-click to reset • Click a point to pin tooltip
Interactivity is the rate at which a single user receives generated tokens while the model streams its answer — how quickly new words appear on screen. Higher values feel snappier; operators trade it against batch throughput.
How many total tokens (input + output) one US dollar of infrastructure spend buys, priced with the all-in hourly ownership cost of a Neocloud Giant operator. It is the reciprocal of cost per token, so higher means cheaper.
Formula: tok/$ = (total tok/s/chip × 3,600) ÷ all-in cost per chip-hour ($)