DeepSeekv4 Pro 0813 1.6T · Performance per Dollar

DeepSeekv4 Pro 0813 1.6T — MI300X vs MI325X Performance per Dollar

Cost per million tokens of MI300X (AMD CDNA 3) versus MI325X (AMD CDNA 3) on DeepSeekv4 Pro 0813 1.6T. 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.

MI300X: $0.90 per million tokens. MI325X: $0.79. Both at 12 tok/s/user on DeepSeekv4 Pro 0813 1.6T, with MI325X 14% cheaper.

Around the middle of the 5–32 tok/s/user interactivity band — at 19 tok/s/user — MI300X runs $2.03 per million tokens on DeepSeekv4 Pro 0813 1.6T while MI325X runs $1.47. MI325X is the cheaper choice by 38%.

On DeepSeekv4 Pro 0813 1.6T at 25 tok/s/user, the per-million math comes out to $2.99 for MI300X and $2.74 for MI325X; MI325X delivers 9% more output per dollar. (Numbers reflect the default 1k/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): MI300X $0.95/chip/hr · MI325X $1.10/chip/hr. Source: SemiAnalysis Market July 2026 Pricing Surveys & AI Cloud TCO Model.

View full latency + throughput comparison →

DeepSeekv4 Pro 0813 1.6T: MI300X versus MI325X cost per million tokens at matched interactivity levels
MI300X versus MI325X 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
MI300X:$0.903MI325X:$0.790
MI300X:$2.030MI325X:$1.474
MI300X:$2.992MI325X:$2.743
Concurrency
MI300X:~101MI325X:~136
MI300X:~29MI325X:~46
MI300X:~15MI325X:~18

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

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