MiniMax M3 428B · Performance per Dollar

MiniMax M3 428B — B300 vs Vera Rubin NVL72 Performance per Dollar

Cost per million tokens of B300 (NVIDIA Blackwell) versus Vera Rubin NVL72 (NVIDIA Vera Rubin) on MiniMax M3 428B. Large-hyperscaler-volume ownership TCO normalized by total 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 →

Vera Rubin NVL72 edges B300 at 162 tok/s/user on MiniMax M3 428B — $0.01 per million tokens versus $0.02, a 90% cost-per-token gap.

Push MiniMax M3 428B to 238 tok/s/user and B300 lands at $0.03 per million tokens against Vera Rubin NVL72's $0.01 — Vera Rubin NVL72 pulls ahead by 126%.

B300: $0.09 per million tokens. Vera Rubin NVL72: $0.02. Both at 315 tok/s/user on MiniMax M3 428B, with Vera Rubin NVL72 344% cheaper. (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.)

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

View full latency + throughput comparison →

MiniMax M3 428B: B300 versus Vera Rubin NVL72 cost per million tokens at matched interactivity levels
B300 versus Vera Rubin NVL72 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.017Vera Rubin NVL72:$0.009
B300:$0.030Vera Rubin NVL72:$0.013
B300:$0.088Vera Rubin NVL72:$0.020
Concurrency
B300:~21Vera Rubin NVL72:~37
B300:~14Vera Rubin NVL72:~20
B300:~2Vera Rubin NVL72:~28

Inference Performance

Agentic inference metrics from the AgentX scenario and fixed-sequence inference metrics across models, hardware configurations, and serving parameters.

Benchmark Config

MiniMax M3 428B 8K / 1K Cost per Million Total Tokens vs. Interactivity

Cost Tier:
Source:
SemiAnalysis InferenceX™

TCO $/chip/hr:

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

Matching measurements exist, but their chip series are hidden.

Shift+Scroll to zoom • Drag to pan • Double-click to reset • Click a point to pin tooltip