Qwen 3.5 397B-A17B · Performance per Dollar

Qwen 3.5 397B-A17B — GB200 NVL72 vs RTX PRO 6000 Performance per Dollar

Cost per million tokens of GB200 NVL72 (NVIDIA Blackwell) 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.

GB200 NVL72 costs $0.09 per million tokens at 118 tok/s/user on Qwen 3.5 397B-A17B; we have no RTX PRO 6000 benchmark data at this exact target.

At 201 tok/s/user on Qwen 3.5 397B-A17B, GB200 NVL72 comes in at $0.28 per million tokens. RTX PRO 6000 hasn't been benchmarked at this operating point.

Only GB200 NVL72 has cost data at 283 tok/s/user on Qwen 3.5 397B-A17B — $0.63 per million tokens. RTX PRO 6000 is unmeasured at this target. (Numbers reflect the default 8k/1k · fp8 selection for this URL — table and chart below update if you change sequence, precision, or model in the controls.)

Chip pricing (owning hyperscaler): GB200 NVL72 $1.86/chip/hr · RTX PRO 6000 $0.68/chip/hr. Source: SemiAnalysis Market July 2026 Pricing Surveys & AI Cloud TCO Model.

View full latency + throughput comparison →

Qwen 3.5 397B-A17B: GB200 NVL72 versus RTX PRO 6000 cost per million tokens at matched interactivity levels
GB200 NVL72 versus RTX PRO 6000 cost per million tokens for this comparison's canonical default workload. Lower cost indicates better performance per dollar.
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)
Dollar per Million Tokens
GB200 NVL72:$0.086RTX PRO 6000:
GB200 NVL72:$0.276RTX PRO 6000:
GB200 NVL72:$0.632RTX PRO 6000:
Concurrency
GB200 NVL72:~233RTX PRO 6000:
GB200 NVL72:~18RTX PRO 6000:
GB200 NVL72:~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: 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.

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