Qwen 3 14B at FP16 needs 28.0 GB for its weights and 38.7 GB in total at 8K context with 8 concurrent users. That means it fits on a single B300 SXM 288GB. Every figure is computed by tokcalc's open-source capacity model.
| GPUs | Total VRAM | VRAM needed | Decode tok/s | Aggregate tok/s | TTFT | Cost / 1M tok | Fits? |
|---|---|---|---|---|---|---|---|
| 1× B300 | 288 GB | 38.7 GB | 185.7 | 2229 | 341.2 ms | $0.9972 | ✓ |
| 2× B300 | 576 GB | 38.7 GB | 315.7 | 7577 | 186.1 ms | $0.5866 | ✓ |
| 4× B300 | 1152 GB | 38.7 GB | 631.4 | 30309 | 108.0 ms | $0.2933 | ✓ |
| 8× B300 | 2304 GB | 38.7 GB | 1263 | 121234 | 69.0 ms | $0.1466 | ✓ |
| Context | Concurrent users | KV per request | Fits? |
|---|---|---|---|
| 4K | 387 | 687.2 MB | ✓ fits |
| 8K | 193 | 1.34 GB | ✓ fits |
| 33K | 48 | 5.37 GB | ✓ fits |
| 66K | 24 | 10.74 GB | ✓ fits |
| 131K | 12 | 21.47 GB | ✓ fits |
| GPU | GPUs | Aggregate tok/s | Cost / 1M tok |
|---|---|---|---|
| RTX 5090 32GB | 2× | 1697 | $0.1637 |
| AMD MI300X 192GB | 1× | 1476 | $0.4704 |
| A100 40GB SXM4 | 1× | 431.8 | $0.5790 |
| AMD MI325X 288GB | 1× | 1671 | $0.5817 |
| A100 80GB SXM4 | 1× | 557.1 | $0.5983 |
| Intel Gaudi 3 128GB | 1× | 919.3 | $0.6043 |
Yes. Qwen 3 14B at FP16 needs 38.7 GB including the KV cache, and B300 SXM 288GB has 288 GB — so it fits on a single GPU.
185.7 tokens/sec per stream and 2229 tok/s aggregate with continuous batching at 8 concurrent users. Time to first token is 341.2 ms, and inter-token latency is 5.4 ms.
$0.9972 per 1M output tokens at 1× B300 SXM 288GB ($8.00/hr). That is the marginal hardware cost — add idle capacity, ops, and egress for the real figure.
28.0 GB for the weights at FP16, plus 10.7 GB of KV cache for 8 concurrent requests at 8K context — 38.7 GB total. Every extra concurrent user at long context costs more, so leave headroom.
It works. Compare $0.9972 per 1M tokens against the alternatives below — the cheapest option that fits the same workload is 4× RTX 3080 10GB at $0.0772, and the fastest is 1× Cerebras CS-3 (WSE-3) at 5571 tok/s.
Same formulas, your context length, concurrency, and quantisation.