Kimi K2.5/K2.6/K2.7-Code 1T · Performance per Dollar

Kimi K2.5/K2.6/K2.7-Code 1T — B300 vs MI355X Performance per Dollar

Cost per million tokens of B300 (NVIDIA Blackwell) versus MI355X (AMD CDNA 4) on Kimi K2.5/K2.6/K2.7-Code 1T. 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.

Near the low end of the 11–123 tok/s/user interactivity band — at 38 tok/s/user — B300 runs $0.15 per million tokens on Kimi K2.5/K2.6/K2.7-Code 1T while MI355X runs $0.10. MI355X is the cheaper choice by 40%.

On Kimi K2.5/K2.6/K2.7-Code 1T at 67 tok/s/user, the per-million math comes out to $0.23 for B300 and $0.17 for MI355X; MI355X delivers 37% more output per dollar.

At 95 tok/s/user on Kimi K2.5/K2.6/K2.7-Code 1T, B300 costs $0.34 per million tokens; MI355X costs $0.24. MI355X is 42% more cost-efficient at this operating point. (Numbers reflect the default 8k/1k · fp4 selection for this URL — table and chart below update if you change sequence, precision, or model in the controls.)

Chip pricing (owning hyperscaler): B300 $2.26/chip/hr · MI355X $1.50/chip/hr. Source: SemiAnalysis Market July 2026 Pricing Surveys & AI Cloud TCO Model.

View full latency + throughput comparison →

Kimi K2.5/K2.6/K2.7-Code 1T: B300 versus MI355X cost per million tokens at matched interactivity levels
B300 versus MI355X 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
B300:$0.145MI355X:$0.104
B300:$0.229MI355X:$0.167
B300:$0.340MI355X:$0.240
Concurrency
B300:~51MI355X:~102
B300:~19MI355X:~17
B300:~9MI355X:~9

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

Kimi K2.5/2.6/2.7-Code 1T 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