What GPU do I need to run orcarouter/LFM3-1.7B-abliterated?
1.7B parameters, published in BF16. View on Hugging FaceGated
Set up LFM3-1.7B-abliteratedLFM3-1.7B-abliterated is published by orcarouter on Hugging Face, with 586 downloads and 42 likes to date. It's a Lfm3ForCausalLM model built for text-generation, published natively in BF16, and gated: you'll need to accept the model's terms on Hugging Face before downloading weights. Its name carries the abliterated tag.
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) |
|---|---|---|---|---|---|
| BF16 | 3.2 GB | 3.9 GB | RTX 3070 | 1 | $0.132/hr |
| FP8 (quantized) | 1.6 GB | 1.9 GB | RTX 4070 | 1 | $0.154/hr |
| INT4 (quantized) | 0.8 GB | 1.0 GB | RTX 3070 | 1 | $0.132/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 LFM3-1.7B-abliterated at its published (BF16) precision: 1× RTX 3070, at $0.132/hr per GPU ($0.132/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
LFM3-1.7B-abliterated: 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.
KV-cache size for LFM3-1.7B-abliterated is not published for this architecture, so no figure is shown.
LFM3-1.7B-abliterated: common questions
How much VRAM does LFM3-1.7B-abliterated need?
3.9 GB at BF16, 1.9 GB at FP8 (quantized), 1.0 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 3.2 GB of weights plus inference overhead is the whole requirement.
Do I need approval to download LFM3-1.7B-abliterated?
Yes. orcarouter gates this repository on Hugging Face, so you have to accept its terms with a signed-in account before the weights will download. It does not change the 3.9 GB the model needs once you have them.
How many copies of LFM3-1.7B-abliterated fit on one RTX 3070?
2, by VRAM alone. That card carries 8.0 GB and one copy needs 3.9 GB at BF16, on a live rate of $0.132/hr for the whole card. Throughput is not modelled here, so 2 copies is not 2 times the requests served.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
Lineage
Based on LFM3-1.7B.
Alternatives at this size
Other models for text-generation within about a third of LFM3-1.7B-abliterated's 1.7B parameters, from other model lines.
- Qwen2.5-1.5B-Instruct (1.5B, BF16)
- Llama-3.2-1B-Instruct (1.2B, BF16)
- OLMo-2-0425-1B (1.5B, F32)
- LFM2.5-1.2B-Instruct (1.2B, BF16)
- SmolLM2-1.7B (1.7B, BF16)
More on LFM3-1.7B-abliterated
Fits on an 8 GB GPU at BF16: every model that fits in 8 GB.
Related reading: RTX 3070 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, Best GPU for LLM inference, and What AI model fine-tuning is.
