on

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

62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly (tight fit)

Slow (tight fit). At Q4_K_M it needs about 8.8 GB of 10.0 GB usable and makes one decision in about 692 ms.

Best quant
Q4_K_M
Time per decision
692 ms
Decisions per second
1.4/s
Input assumed
512 tokens
Returns
Fixed labels

Best app to run it on the Intel Arc B570

On Windows

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

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

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).

How it’s rated

Quality 62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q4_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: S 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Slowtight fit
How well it runs on the Intel Arc B570: 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.2 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.24.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.5.7 / 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 score69.9 / 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 B570

Quant Memory needed Available Time per decision Runs Quality Download
Q4_K_M 8.8 GB 10.0 GB 692 ms Slowtight fit 62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 10.0 GB 10.0 GB 737 ms Slowoffloads to RAM 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 11.3 GB 10.0 GB 965 ms Slowoffloads to RAM 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 14.2 GB 10.0 GB 1.5 s Very slowheavy RAM offload 66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 25.5 GB 10.0 GB 3.6 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

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.