What GPU do I need to run bigscience/bloom-3b?
3.0B parameters, published in F16. View on Hugging Face
Set up bloom-3bbloom-3b is published by bigscience on Hugging Face, with 18,064 downloads and 94 likes to date. It's a BloomForCausalLM model built for text-generation, published natively in F16.
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) |
|---|---|---|---|---|---|
| FP16 | 5.6 GB | 6.7 GB | P4 | 1 | $0.069/hr |
| FP8 (quantized) | 2.8 GB | 3.4 GB | RTX 4070 Super | 1 | $0.121/hr |
| INT4 (quantized) | 1.4 GB | 1.7 GB | RTX 3060 | 1 | $0.110/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 bloom-3b at its published (F16) precision: 1× P4, at $0.069/hr per GPU ($0.069/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
bloom-3b: 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: 307,200 bytes at 16-bit.
The model's maximum context length is not published in its configuration, so no per-context figures are shown.
Computed from the layer, head and window counts in the model's own configuration (bigscience/bloom-3b), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.
bloom-3b: common questions
Does bloom-3b fit on a 8 GB GPU?
Yes. At FP16 it needs 6.7 GB of VRAM, so an 8 GB card holds it with 1.3 GB to spare. A 6 GB card is not enough for it at FP16.
What is the least VRAM bloom-3b can run in?
1.7 GB, at INT4 (quantized), which fits a 6 GB card, against 6.7 GB at FP16. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More BLOOM models
- bloom-1b7 (1.7B, F16)
- bloom-1b1 (1.1B, F16)
- bloomz-560m (559M, F16)
- bloom-560m (559M, F16)
- bloom (176.2B, BF16)
Alternatives at this size
Other models for text-generation within about a third of bloom-3b's 3.0B parameters, from other model lines.
- Qwen2.5-3B-Instruct (3.1B, BF16)
- phi-2 (2.8B, F16)
- Llama-3.2-3B-Instruct (3.2B, BF16)
- PowerMoE-3b (3.4B, F32)
- gemma-2-2b-it (2.6B, BF16)
More on bloom-3b
Fits on an 8 GB GPU at FP16: every model that fits in 8 GB.
Best chat and assistants models: how bloom-3b ranks against the rest.
Related reading: H100 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.
