Qwen 3.5 397B-A17B — H200 vs RTX PRO 6000 Performance per Dollar
Cost per million tokens of H200 (NVIDIA Hopper) versus RTX PRO 6000 (NVIDIA Blackwell) on Qwen 3.5 397B-A17B. 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.
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 →
Only H200 has cost data at 99 tok/s/user on Qwen 3.5 397B-A17B — $0.04 per million tokens. RTX PRO 6000 is unmeasured at this target.
H200 costs $0.06 per million tokens at 146 tok/s/user on Qwen 3.5 397B-A17B; we have no RTX PRO 6000 benchmark data at this exact target.
At 193 tok/s/user on Qwen 3.5 397B-A17B, H200 comes in at $0.13 per million tokens. RTX PRO 6000 hasn't been benchmarked at this operating point. (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.)
Chip pricing (owning hyperscaler): H200 $1.22/chip/hr · RTX PRO 6000 $0.68/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.042RTX PRO 6000:— | H200:$0.063RTX PRO 6000:— | H200:$0.131RTX PRO 6000:— |
| Concurrency | H200:~13RTX PRO 6000:— | H200:~9RTX PRO 6000:— | H200:~4RTX PRO 6000:— |
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
Qwen3.5 397B • 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