Kimi K2.5/K2.6/K2.7-Code 1T — H200 vs MI355X Performance per Dollar
Cost per million tokens of H200 (NVIDIA Hopper) versus MI355X (AMD CDNA 4) on Kimi K2.5/K2.6/K2.7-Code 1T. 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.
MI355X edges H200 at 32 tok/s/user on Kimi K2.5/K2.6/K2.7-Code 1T — $0.26 per million tokens versus $0.36, a 37% cost-per-token gap.
Push Kimi K2.5/K2.6/K2.7-Code 1T to 48 tok/s/user and H200 lands at $0.43 per million tokens against MI355X's $0.37 — MI355X pulls ahead by 15%.
H200: $0.52 per million tokens. MI355X: $0.50. Both at 63 tok/s/user on Kimi K2.5/K2.6/K2.7-Code 1T, with MI355X 4% cheaper. (Numbers reflect the default 8k/1k · int4 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 · MI355X $1.50/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.357MI355X:$0.261 | H200:$0.428MI355X:$0.371 | H200:$0.517MI355X:$0.496 |
| Concurrency | H200:~27MI355X:~23 | H200:~15MI355X:~11 | H200:~10MI355X:~6 |
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
Kimi K2.5/2.6/2.7-Code 1T • 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