Can the Intel Arc B580 run Llama Guard 4 12B?

Yes, but slowly

Slow. At Q5_K_M it needs about 10.1 GB of 12.0 GB usable and makes one decision in about 617 ms.

Best quant: Q5_K_M
Time per decision: 617 ms
Decisions per second: 1.6/s
Input assumed: 512 tokens
Returns: Fixed labels

Best app to run it on the Intel Arc B580

On Windows

Command line + local API · runs on llama.cpp, vLLM

Handy if you already work in Docker.

docker model run hf.co/meta-llama/Llama-Guard-4-12B

Sentence Transformers Can only use the CPU on this hardware, so it will be slow.

On Linux

Docker Model Runner

Command line + local API · runs on llama.cpp, vLLM

Handy if you already work in Docker.

docker model run hf.co/meta-llama/Llama-Guard-4-12B

Sentence Transformers Can only use the CPU on this hardware, so it will be slow.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Llama Guard 4 12B

Original weights · Hugging Face

Full-precision files from Meta, for fine-tuning, vLLM, Transformers.

huggingface.co/meta-llama/Llama-Guard-4-12B (opens in a new tab)

Free Hugging Face account needed: request access on the model page, and Meta approves it (usually within minutes to a few hours).

Links checked 7 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q5_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Slow: How well it runs on the Intel Arc B580: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.	28.8 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	25.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.	6.0 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.	12.0 / 15
Match score	71.8 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Intel Arc B580

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q4_K_M`	8.9 GB	12.0 GB	582 ms	Slow	62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q5_K_M`	10.1 GB	12.0 GB	617 ms	Slow	64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q6_K`	11.4 GB	12.0 GB	656 ms	Slowtight fit	65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q8_0`	14.3 GB	12.0 GB	1.1 s	Slowoffloads to RAM	66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`F16`	25.6 GB	12.0 GB	3.1 s	Very slowheavy RAM offload	66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 48/100 (quality, fit, speed and memory use) sets the ranking.	Original weights (opens in a new tab)

Times are for one request with a 512-token input and about 6 tokens written. Batching servers process many requests at once.

Other hardware that runs it

65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Q6_K · 119 ms · Runs great
65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q6_K · 133 ms · Runs great
65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX Q6_K · 187 ms · Runs well
65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 Q6_K · 191 ms · Runs well
65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 Q6_K · 244 ms · Runs well
65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT Q6_K · 259 ms · Runs well

Quick answers

How much memory does Llama Guard 4 12B need on the Arc B580 12GB?

At Q5_K_M it needs about 10.1 GB. The Arc B580 12GB has 12.0 GB usable.

How fast is Llama Guard 4 12B on the Arc B580 12GB?

It makes one decision in about 617 ms at Q5_K_M, an estimate from the hardware and the size of the model.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.