What GPU do I need to run allenai/OLMo-1B-hf?
1.2B parameters, published in F32. View on Hugging Face
Set up OLMo-1B-hfOLMo-1B-hf is published by allenai on Hugging Face, with 51,542 downloads and 29 likes to date. It's a OlmoForCausalLM model built for text-generation, published natively in F32.
VRAM required & cheapest live GPU fit
Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.
| Precision | Weight size | Required VRAM | Cheapest live fit | GPUs needed | Est. $/hr (full fit) |
|---|---|---|---|---|---|
| FP32 | 4.4 GB | 5.3 GB | V100 | 1 | $0.088/hr |
| FP8 (quantized) | 1.1 GB | 1.3 GB | RTX 4070 Super | 1 | $0.121/hr |
| INT4 (quantized) | 0.5 GB | 0.7 GB | RTX 4070 Super | 1 | $0.121/hr |
A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.
INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.
Cheapest way to run OLMo-1B-hf at its published (F32) precision: 1× V100, at $0.088/hr per GPU ($0.088/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
OLMo-1B-hf: KV cache by context length
The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.
Multi-head attention: every layer caches keys and values for every head. Cached per token: 131,072 bytes at 16-bit.
| Context | KV cache, one sequence |
|---|---|
| 2K (model maximum) | 0.25 GB |
Computed from the layer, head and window counts in the model's own configuration (allenai/OLMo-1B-hf), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.
OLMo-1B-hf: common questions
How much VRAM does OLMo-1B-hf need?
5.3 GB at FP32, 1.3 GB at FP8 (quantized), 0.7 GB at INT4 (quantized). All of those sit under 6 GB, the smallest capacity this page reasons about, so VRAM is not what limits where this model runs. The 4.4 GB of weights plus inference overhead is the whole requirement.
Can OLMo-1B-hf run in 16-bit instead of FP32?
Yes. Its published weights are FP32, 4.4 GB, or 5.3 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 2.2 GB, or 2.6 GB with overhead. How much accuracy the cast costs is model-specific and is not measured here.
How many copies of OLMo-1B-hf fit on one V100?
3, by VRAM alone. That card carries 16.0 GB and one copy needs 5.3 GB at FP32, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 3 copies is not 3 times the requests served.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More OLMo 1 models
- OLMo-7B-hf (6.9B, F32)
Alternatives at this size
Other models for text-generation within about a third of OLMo-1B-hf's 1.2B parameters, from other model lines.
- Qwen2.5-1.5B-Instruct (1.5B, BF16)
- Llama-3.2-1B-Instruct (1.2B, BF16)
- gemma-3-1b-it (1000M, BF16)
- OpenELM-1_1B-Instruct (1.1B, BF16)
- gpt2-large (812M, F32)
More on OLMo-1B-hf
Fits on an 8 GB GPU at FP32: every model that fits in 8 GB.
Best chat and assistants models: how OLMo-1B-hf ranks against the rest.
Related reading: V100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.
