Head-to-head AI inference benchmark comparison of H200 (NVIDIA Hopper) and MI300X (AMD CDNA 3) 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 →
Setting 27 tok/s/user as the target on MiniMax M3 428B, H200 produces 3883 tok/s/chip ($0.09 per million tokens) and MI300X produces 973 ($0.27). H200 is 211% cheaper per token; H200 delivers 299% more tok/s/chip.
At 28 tok/s/user interactivity on MiniMax M3 428B, H200 delivers 3727 tok/s/chip at $0.09 per million tokens; MI300X delivers 953 tok/s/chip at $0.28. H200 is 205% cheaper per token; H200 delivers 291% more tok/s/chip at this point.
H200 posts 3568 tok/s/chip for $0.09 per million tokens at 29 tok/s/user on MiniMax M3 428B; MI300X posts 934 tok/s/chip for $0.28. H200 is 197% cheaper per token; H200 delivers 282% 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) | H200:3883.0MI300X:973.3 | H200:3727.2MI300X:952.5 | H200:3568.3MI300X:934.4 |
| Cost ($/M tok) | H200:$0.087MI300X:$0.271 | H200:$0.091MI300X:$0.277 | H200:$0.095MI300X:$0.282 |
| tok/s/MW | H200:2834336MI300X:700190 | H200:2720611MI300X:685259 | H200:2604605MI300X:672218 |
| Concurrency | H200:~10MI300X:~2 | H200:~9MI300X:~2 | H200:~9MI300X:~2 |
Agentic inference metrics from the AgentX scenario and fixed-sequence inference metrics across models, hardware configurations, and serving parameters.
TCO $/chip/hr:
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 measurements to plot for this selection. Review the benchmark controls above or adjust quick filters.
Shift+Scroll to zoom • Drag to pan • Double-click to reset • Click a point to pin tooltip