Qwen 3.5 397B-A17B · Chip comparison

Qwen 3.5 397B-A17B — GB300 NVL72 vs MI355X

Head-to-head AI inference benchmark comparison of GB300 NVL72 (NVIDIA Blackwell) 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

GB300 NVL72 / MI355X on Qwen 3.5 397B-A17B at 38 tok/s/user: 150385 / 19719 tok/s/chip, $0.00 / $0.02 per million tokens. GB300 NVL72 is 395% cheaper per token; GB300 NVL72 delivers 663% more tok/s/chip.

Around the middle of the 24–79 tok/s/user interactivity band, at 52 tok/s/user on Qwen 3.5 397B-A17B: GB300 NVL72 runs 150385 tok/s/chip at $0.00/M tokens, MI355X runs 10760 at $0.04/M. GB300 NVL72 is 808% cheaper per token; GB300 NVL72 delivers 1298% more tok/s/chip.

Setting 66 tok/s/user as the target on Qwen 3.5 397B-A17B, GB300 NVL72 produces 150385 tok/s/chip ($0.00 per million tokens) and MI355X produces 7349 ($0.06). GB300 NVL72 is 1229% cheaper per token; GB300 NVL72 delivers 1946% more tok/s/chip. (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.)

View performance-per-dollar view →

Interpolated from real benchmark data. Edit target interactivity values below to compare at different operating points.
Metric
Interactivity (tok/s/user)
Interactivity (tok/s/user)
Interactivity (tok/s/user)
Throughput (tok/s/chip)
GB300 NVL72:150384.7MI355X:19719.4
GB300 NVL72:150384.7MI355X:10760.1
GB300 NVL72:150384.7MI355X:7349.1
Cost ($/M tok)
GB300 NVL72:$0.004MI355X:$0.021
GB300 NVL72:$0.004MI355X:$0.039
GB300 NVL72:$0.004MI355X:$0.057
tok/s/MW
GB300 NVL72:70936182MI355X:9435120
GB300 NVL72:70936182MI355X:5148354
GB300 NVL72:70936182MI355X:3516331
Concurrency
GB300 NVL72:~704MI355X:~13
GB300 NVL72:~704MI355X:~12
GB300 NVL72:~704MI355X:~7

Inference Performance

Agentic inference metrics from the AgentX scenario and fixed-sequence inference metrics across models, hardware configurations, and serving parameters.

Total Tokens per $1 USD (Owning - Neocloud Giant) vs. Interactivity

Qwen3.5 397B FP4 8K / 1K Source: SemiAnalysis InferenceX™

TCO $/chip/hr: VR200: 3.61H100: 1.55H200: 1.59B200: 2.07B300: 2.52GB200: 2.26GB300: 2.79MI300X: 1.16MI325X: 1.32MI355X: 2.09RTX6000PRO: 0.75Jalapeño (Teacup): 1.56

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

1 The ATOM engine is promising, however it has yet to serve production tokens. It is still in its infant stage.