Head-to-head AI inference benchmark comparison of MI355X (AMD CDNA 4) and TPU7x (Google Ironwood) 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 →
Throughput at 140 tok/s/user on Qwen 3.5 397B-A17B: MI355X hits 29591 tok/s/chip, TPU7x hits 38001. Per-million costs land at $0.01 and $0.01 respectively. TPU7x is 87% cheaper per token; TPU7x delivers 28% more tok/s/chip.
MI355X / TPU7x on Qwen 3.5 397B-A17B at 198 tok/s/user: 16021 / 34575 tok/s/chip, $0.03 / $0.01 per million tokens. TPU7x is 214% cheaper per token; TPU7x delivers 116% more tok/s/chip.
Toward the upper edge of the 82–314 tok/s/user interactivity band, at 256 tok/s/user on Qwen 3.5 397B-A17B: MI355X runs 5299 tok/s/chip at $0.08/M tokens, TPU7x runs 26730 at $0.01/M. TPU7x is 635% cheaper per token; TPU7x delivers 404% 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) | MI355X:29591.3TPU7x:38000.7 | MI355X:16021.5TPU7x:34574.8 | MI355X:5298.7TPU7x:26730.3 |
| Cost ($/M tok) | MI355X:$0.014TPU7x:$0.008 | MI355X:$0.026TPU7x:$0.008 | MI355X:$0.079TPU7x:$0.011 |
| tok/s/MW | MI355X:14158533TPU7x:31483606 | MI355X:7665781TPU7x:28645212 | MI355X:2535266TPU7x:22146054 |
| Concurrency | MI355X:~22TPU7x:~26 | MI355X:~11TPU7x:~23 | MI355X:~3TPU7x:~17 |
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.
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.