Llama 3.3 70B — H200 vs MI300X Performance per Dollar
Cost per million tokens of H200 (NVIDIA Hopper) versus MI300X (AMD CDNA 3) on Llama 3.3 70B. 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.
H200: $0.09 per million tokens. MI300X: $0.19. Both at 44 tok/s/user on Llama 3.3 70B, with H200 109% cheaper.
Around the middle of the 22–112 tok/s/user interactivity band — at 67 tok/s/user — H200 runs $0.14 per million tokens on Llama 3.3 70B while MI300X runs $0.31. H200 is the cheaper choice by 120%.
On Llama 3.3 70B at 90 tok/s/user, the per-million math comes out to $0.22 for H200 and $0.65 for MI300X; H200 delivers 188% more output per dollar. (Numbers reflect the default 1k/1k · fp8 selection for this URL — table and chart below update if you change sequence, precision, or model in the controls.)
Chip pricing (owning hyperscaler): H200 $1.22/chip/hr · MI300X $0.95/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 | H200:$0.090MI300X:$0.188 | H200:$0.142MI300X:$0.313 | H200:$0.224MI300X:$0.646 |
| Concurrency | H200:~96MI300X:~64 | H200:~64MI300X:~32 | H200:~37MI300X:~20 |
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
Llama 3.3 70B Instruct • 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