Hardware · Memory
How much memory does a model need?
Pick an LLM and a context length. We add up the weights at every quantization, the KV cache that grows with context, and runtime overhead, then show the smallest systems and devices that hold it.
Trinity Large Thinking (400B-A13B) at 8K context
| Quantization | Weights | KV cache + overhead | Total | Smallest hardware that holds it |
|---|---|---|---|---|
Q2_K |
159 GB | 1.3 GB | 161 GB | |
Q3_K_M |
195 GB | 1.3 GB | 197 GB | |
Q4_K_M |
243 GB | 1.3 GB | 244 GB | |
Q5_K_M |
283 GB | 1.3 GB | 284 GB | |
Q6_K |
327 GB | 1.3 GB | 328 GB | |
Q8_0 |
423 GB | 1.3 GB | 424 GB | |
F16 |
797 GB | 1.3 GB | 799 GB |
The rule of thumb
1 · WeightsParameters × bytes eachA 70B model at 4 bits per weight is about 70 × 0.6 ≈ 42 GB. Lower quantization shrinks it and costs some quality.
2 · KV cacheGrows with contextEvery token you keep in context stores keys and values for each layer. Doubling context doubles this part, so long documents cost real memory.
3 · OverheadLeave headroomThe runtime, the operating system and other apps need memory too. Aim for a total at least 10% under the memory your GPU or device can give a model.
Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.