MiniMax M3 428B — H100 vs H200 Performance per Dollar
Cost per million tokens of H100 (NVIDIA Hopper) versus H200 (NVIDIA Hopper) on MiniMax M3 428B. Owning-hyperscaler TCO normalized by output tokens — performance per dollar across LLM workloads. Pick the more cost-efficient SKU at every target interactivity level. 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 →
Near the low end of the 7–54 tok/s/user interactivity band — at 18 tok/s/user — H100 runs $0.57 per million tokens on MiniMax M3 428B while H200 runs $0.08. H200 is the cheaper choice by 654%.
On MiniMax M3 428B at 30 tok/s/user, the per-million math comes out to $0.57 for H100 and $0.12 for H200; H200 delivers 371% more output per dollar.
At 42 tok/s/user on MiniMax M3 428B, H100 costs $0.57 per million tokens; H200 costs $0.24. H200 is 140% more cost-efficient at this operating point. (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.)
Chip pricing (owning hyperscaler): H100 $1.17/chip/hr · H200 $1.22/chip/hr. Source: SemiAnalysis Market July 2026 Pricing Surveys & AI Cloud TCO Model.
| Metric | Interactivity (tok/s/user) | Interactivity (tok/s/user) | Interactivity (tok/s/user) |
|---|---|---|---|
| Dollar per Million Tokens | H100:$0.572H200:$0.076 | H100:$0.572H200:$0.121 | H100:$0.572H200:$0.238 |
| Concurrency | H100:~1H200:~14 | H100:~1H200:~7 | H100:~1H200:~3 |
Inference Performance
Agentic inference metrics from the AgentX scenario and fixed-sequence inference metrics across models, hardware configurations, and serving parameters.
Cost per Million Total Tokens (Owning - Hyperscaler) vs. Interactivity
MiniMax M3 428B • FP4 • 8K / 1K • Source: SemiAnalysis InferenceX™
TCO $/chip/hr: H100: 1.17H200: 1.22B200: 1.73B300: 2.26GB200: 1.86GB300: 2.31MI300X: 0.95MI325X: 1.1MI355X: 1.5RTX6000PRO: 0.68
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