What GPU do I need to run bigscience/bloom-1b1?
1.1B parameters, published in F16. View on Hugging Face
Set up bloom-1b1bloom-1b1 is published by bigscience on Hugging Face, with 11,269 downloads and 67 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 | 2.0 GB | 2.4 GB | V100 | 1 | $0.088/hr |
| FP8 (quantized) | 1.0 GB | 1.2 GB | RTX 4000 SFF Ada | 1 | $0.198/hr |
| INT4 (quantized) | 0.5 GB | 0.6 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-1b1 at its published (F16) 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.
bloom-1b1: 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: 147,456 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-1b1), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.
bloom-1b1: common questions
How much VRAM does bloom-1b1 need?
2.4 GB at FP16, 1.2 GB at FP8 (quantized), 0.6 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 2.0 GB of weights plus inference overhead is the whole requirement.
How many copies of bloom-1b1 fit on one V100?
6, by VRAM alone. That card carries 16.0 GB and one copy needs 2.4 GB at FP16, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 6 copies is not 6 times the requests served.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More BLOOM models
- bloom-1b7 (1.7B, F16)
- bloomz-560m (559M, F16)
- bloom-560m (559M, F16)
- bloom-3b (3.0B, F16)
- bloom (176.2B, BF16)
Alternatives at this size
Other models for text-generation within about a third of bloom-1b1's 1.1B parameters, from other model lines.
- Qwen3-0.6B (752M, 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 bloom-1b1
Fits on an 8 GB GPU at FP16: every model that fits in 8 GB.
Best chat and assistants models: how bloom-1b1 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.
