OLMo 2 13B needs 26.0 GB of VRAM for its weights at FP16 — 26.7 GB once a KV cache is loaded. Below is the full breakdown: which GPUs fit, how many you need, what it serves, and what it costs per million tokens. Every figure comes from tokcalc's open-source capacity model.
| Quantization | Weights | With KV cache | Smallest single GPU |
|---|---|---|---|
| FP16recommended | 26.0 GB | 26.7 GB | V100 SXM2 32GB (32 GB) |
| FP8 (E4M3) | 13.0 GB | 13.7 GB | T4 16GB (16 GB) |
| AWQ 4-bit | 7.2 GB | 7.8 GB | RTX 3080 10GB (10 GB) |
| GPU | GPUs | Total VRAM | Decode tok/s | Aggregate tok/s | Cost / 1M tokens |
|---|---|---|---|---|---|
| RTX 3080 10GB | 4× | 40 GB | 64.60 | 3101 | $0.0717 |
| RTX 4080 16GB | 4× | 64 GB | 60.95 | 2925 | $0.1139 |
| RTX 3090 24GB | 2× | 48 GB | 39.78 | 954.7 | $0.1455 |
| RTX 5090 32GB | 2× | 64 GB | 76.16 | 1828 | $0.1520 |
| T4 16GB | 4× | 64 GB | 27.20 | 1306 | $0.1702 |
| RTX A4000 16GB | 4× | 64 GB | 38.08 | 1828 | $0.1824 |
| RTX 4090 24GB | 2× | 48 GB | 42.84 | 1028 | $0.2161 |
| V100 SXM2 32GB | 2× | 64 GB | 38.25 | 918.0 | $0.3026 |
| A10G 24GB | 2× | 48 GB | 25.50 | 612.0 | $0.3268 |
| AMD MI300X 192GB | 1× | 192 GB | 132.5 | 1590 | $0.4368 |
| TPU v6e Trillium (32GB) | 2× | 64 GB | 34.81 | 835.4 | $0.5320 |
| A100 40GB SXM4 | 1× | 40 GB | 38.75 | 465.0 | $0.5376 |
RTX 3080 10GB has no NVLink, so 4-way tensor parallelism runs over PCIe. tokcalc applies a flat 0.85× multi-GPU efficiency factor for this, which is realistic for NVLink-equipped datacenter cards but optimistic for PCIe scale-out — treat the throughput and cost figures for this configuration as an upper bound, and measure before committing.
| Context | Concurrent users | KV per request | Fits? |
|---|---|---|---|
| 4K | 20 | 687.2 MB | ✓ fits |
| 8K | 10 | 1.34 GB | ✓ fits |
| 33K | 2 | 5.37 GB | ✓ fits |
| 66K | 1 | 10.74 GB | ✓ fits |
| 131K | 0 | 21.47 GB | ✗ does not fit |
Yes. At FP16 the model needs 26.7 GB of VRAM, so it fits on a single A100 40GB SXM4 or anything with more VRAM. At full FP16 it needs 26.7 GB, which fits on one V100 SXM2 32GB or larger.
At FP16 with 8,192-token context and 8 concurrent users, the cheapest configuration that fits is 4× RTX 3080 10GB (40 GB total VRAM). $0.0717 per 1M output tokens.
On 1× Cerebras CS-3 (WSE-3) at FP16, the aggregate throughput is 6000 tokens/sec with continuous batching. That hardware has no published rental price, so its cost per million tokens is not comparable.
Weights alone: 26.0 GB at FP16, 26.0 GB at FP16. Add KV cache for your context length and concurrency — every concurrent request at 8,192 tokens costs extra VRAM, so budget headroom above the weight figure.
At 4× RTX 3080 10GB the marginal cost is $0.0717 per 1M output tokens, before you add idle capacity, ops staff, or egress. That is typically cheaper than frontier API pricing at sustained volume, but API calls win when your load is bursty or too small to keep a GPU busy. The Build vs Buy tab on tokcalc prices this against a specific provider for you.
The calculator uses the exact same formulas as this page — change the workload and watch every number update.
| Total parameters | 13.00B |
| Active parameters per token | 13.00B |
| Architecture | Dense |
| Attention layout | Full attention (GQA) |
| Transformer layers | 40 |
| Hidden dimension | 5120 |
| Attention heads | 40 query / 8 KV (GQA) |
| Head dimension | 128 |
| Vocabulary size | 50,281 |
| Max context (catalog) | 4K |
| KV cache per token @ 8K | 160.0 KB |
Every layer caches keys and values for the whole context, so the KV cache grows linearly with conversation length.