Head-to-head AI inference benchmark comparison of H200 (NVIDIA Hopper) and MI355X (AMD CDNA 4) on Qwen 3.5 397B-A17B. 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 →
At 79 tok/s/user on Qwen 3.5 397B-A17B, MI355X delivers 36933 tok/s/chip at $0.01 per million tokens; H200 hasn't been benchmarked at this target.
MI355X hits 20063 tok/s/chip for $0.02 per million tokens at 134 tok/s/user on Qwen 3.5 397B-A17B. No H200 data at this operating point.
MI355X: 10353 tok/s/chip, $0.04 per million tokens at 189 tok/s/user on Qwen 3.5 397B-A17B. H200 is unmeasured here. (Numbers reflect the default agentic-traces · fp4 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:—MI355X:36932.6 | H200:—MI355X:20063.1 | H200:—MI355X:10353.1 |
| Cost ($/M tok) | H200:—MI355X:$0.011 | H200:—MI355X:$0.021 | H200:—MI355X:$0.040 |
| tok/s/MW | H200:—MI355X:17671124 | H200:—MI355X:9599552 | H200:—MI355X:4953631 |
| Concurrency | H200:—MI355X:~15 | H200:—MI355X:~12 | H200:—MI355X:~3 |
Agentic inference metrics from the AgentX scenario and fixed-sequence inference metrics across models, hardware configurations, and serving parameters.
TCO $/chip/hr: VR200: 3.61H100: 1.17H200: 1.22B200: 1.73B300: 2.26GB200: 1.86GB300: 2.31MI300X: 0.95MI325X: 1.1MI355X: 1.5RTX6000PRO: 0.68Jalapeño (Teacup): 1.47
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.
Matching measurements exist, but their chip series are hidden.
Shift+Scroll to zoom • Drag to pan • Double-click to reset • Click a point to pin tooltip
1 The ATOM engine is promising, however it has yet to serve production tokens. It is still in its infant stage.
Qwen3.5 397B 8K / 1K Total Tokens per $1 TCO vs. Interactivity