DeepSeekv4 Pro 0813 1.6T · Chip comparison

DeepSeekv4 Pro 0813 1.6T — B200 vs MI355X

Head-to-head AI inference benchmark comparison of B200 (NVIDIA Blackwell) and MI355X (AMD CDNA 4) on DeepSeekv4 Pro 0813 1.6T. 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

Near the low end of the 17–121 tok/s/user interactivity band, at 43 tok/s/user on DeepSeekv4 Pro 0813 1.6T: B200 runs 28897 tok/s/chip at $0.02/M tokens, MI355X runs 12701 at $0.03/M. B200 is 97% cheaper per token; B200 delivers 128% more tok/s/chip.

Setting 69 tok/s/user as the target on DeepSeekv4 Pro 0813 1.6T, B200 produces 11397 tok/s/chip ($0.04 per million tokens) and MI355X produces 8373 ($0.05). B200 is 18% cheaper per token; B200 delivers 36% more tok/s/chip.

At 95 tok/s/user interactivity on DeepSeekv4 Pro 0813 1.6T, B200 delivers 7119 tok/s/chip at $0.07 per million tokens; MI355X delivers 4878 tok/s/chip at $0.09. B200 is 27% cheaper per token; B200 delivers 46% more tok/s/chip at this point. (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)
B200:28897.0MI355X:12700.6
B200:11396.6MI355X:8372.9
B200:7119.2MI355X:4877.7
Cost ($/M tok)
B200:$0.017MI355X:$0.033
B200:$0.042MI355X:$0.050
B200:$0.068MI355X:$0.085
tok/s/MW
B200:16898845MI355X:6076828
B200:6664662MI355X:4006174
B200:4163296MI355X:2333833
Concurrency
B200:~64MI355X:~64
B200:~19MI355X:~6
B200:~10MI355X:~4

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

DeepSeek V4 Pro 0813 1.6T 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.