What GPU do I need to run AcuteShrewdSecurity/Llama-Phishsense-1B?

1.2B parameters, published in BF16. View on Hugging FaceGated

1.2B
Parameters
BF16
Native precision
LlamaForCausalLM
Architecture
text-generation
Pipeline

Llama-Phishsense-1B is published by AcuteShrewdSecurity on Hugging Face, with 45,400 downloads and 8 likes to date. It's a LlamaForCausalLM 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.

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.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF162.3 GB2.8 GBRTX 30701$0.088/hr
FP8 (quantized)1.2 GB1.4 GBRTX 40701$0.154/hr
INT4 (quantized)0.6 GB0.7 GBRTX 30701$0.088/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 Llama-Phishsense-1B at its published (BF16) precision: 1× RTX 3070, 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.

Llama-Phishsense-1B: 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 Llama-Phishsense-1B is not published for this architecture, so no figure is shown.

Llama-Phishsense-1B: common questions

How much VRAM does Llama-Phishsense-1B need?

2.8 GB at BF16, 1.4 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 2.3 GB of weights plus inference overhead is the whole requirement.

Do I need approval to download Llama-Phishsense-1B?

Yes. AcuteShrewdSecurity 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 2.8 GB the model needs once you have them.

How many copies of Llama-Phishsense-1B fit on one RTX 3070?

2, by VRAM alone. That card carries 8.0 GB and one copy needs 2.8 GB at BF16, on a live rate of $0.088/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.

More Llama Guard models

All 4 Llama Guard models: VRAM and GPU requirements

Lineage

Based on Llama-Guard-3-1B.

Alternatives at this size

Other models for text-generation within about a third of Llama-Phishsense-1B's 1.2B parameters, from other model lines.

More on Llama-Phishsense-1B

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.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.