GLM 5.3 744B — B200 vs H200 Performance per Dollar
Cost per million tokens of B200 (NVIDIA Blackwell) versus H200 (NVIDIA Hopper) on GLM 5.3 744B. 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.
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 →
B200 costs $0.07 per million tokens at 143 tok/s/user on GLM 5.3 744B; we have no H200 benchmark data at this exact target.
At 196 tok/s/user on GLM 5.3 744B, B200 comes in at $0.09 per million tokens. H200 hasn't been benchmarked at this operating point.
Only B200 has cost data at 248 tok/s/user on GLM 5.3 744B — $0.12 per million tokens. H200 is unmeasured at this target. (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): B200 $1.73/chip/hr · H200 $1.22/chip/hr. Source: SemiAnalysis Market July 2026 Pricing Surveys & AI Cloud TCO Model.
| Metric | Interactivity (tok/s/user) | Interactivity (tok/s/user) | Interactivity (tok/s/user) |
|---|---|---|---|
| Dollar per Million Tokens | B200:$0.065H200:— | B200:$0.095H200:— | B200:$0.118H200:— |
| Concurrency | B200:~11H200:— | B200:~6H200:— | B200:~4H200:— |
Inference Performance
Agentic inference metrics from the AgentX scenario and fixed-sequence inference metrics across models, hardware configurations, and serving parameters.