OLMo 2 13B at FP16 needs 26.0 GB for its weights and 36.7 GB in total at 8K context with 8 concurrent users. That means it fits on a single H200 SXM5 141GB. 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× H200 | 141 GB | 36.7 GB | 120.0 | 1440 | 468.6 ms | $0.7716 | ✓ |
| 2× H200 | 282 GB | 36.7 GB | 204.0 | 4896 | 250.0 ms | $0.4539 | ✓ |
| 4× H200 | 564 GB | 36.7 GB | 408.0 | 19584 | 140.0 ms | $0.2269 | ✓ |
| 8× H200 | 1128 GB | 36.7 GB | 816.0 | 78336 | 85.0 ms | $0.1135 | ✓ |
| Context | Concurrent users | KV per request | Fits? |
|---|---|---|---|
| 4K | 171 | 687.2 MB | ✓ fits |
| 8K | 85 | 1.34 GB | ✓ fits |
| 33K | 21 | 5.37 GB | ✓ fits |
| 66K | 10 | 10.74 GB | ✓ fits |
| 131K | 5 | 21.47 GB | ✓ fits |
| GPU | GPUs | Aggregate tok/s | Cost / 1M tok |
|---|---|---|---|
| RTX 5090 32GB | 2× | 1828 | $0.1520 |
| AMD MI300X 192GB | 1× | 1590 | $0.4368 |
| A100 40GB SXM4 | 1× | 465.0 | $0.5376 |
| AMD MI325X 288GB | 1× | 1800 | $0.5401 |
| A100 80GB SXM4 | 1× | 600.0 | $0.5556 |
| Intel Gaudi 3 128GB | 1× | 990.0 | $0.5612 |
Yes. OLMo 2 13B at FP16 needs 36.7 GB including the KV cache, and H200 SXM5 141GB has 141 GB — so it fits on a single GPU.
120.0 tokens/sec per stream and 1440 tok/s aggregate with continuous batching at 8 concurrent users. Time to first token is 468.6 ms, and inter-token latency is 8.3 ms.
$0.7716 per 1M output tokens at 1× H200 SXM5 141GB ($4.00/hr). That is the marginal hardware cost — add idle capacity, ops, and egress for the real figure.
26.0 GB for the weights at FP16, plus 10.7 GB of KV cache for 8 concurrent requests at 8K context — 36.7 GB total. Every extra concurrent user at long context costs more, so leave headroom.
It works. Compare $0.7716 per 1M tokens against the alternatives below — the cheapest option that fits the same workload is 4× RTX 3080 10GB at $0.0717, and the fastest is 1× Cerebras CS-3 (WSE-3) at 6000 tok/s.
Same formulas, your context length, concurrency, and quantisation.