on

Can the Intel Arc A380 run ShieldGemma 2B?

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

Yes, it runs well

Runs well. At Q8_0 it needs about 3.9 GB of 6.0 GB usable and makes one decision in about 330 ms.

Best quant
Q8_0
Time per decision
330 ms
Decisions per second
3.0/s
Input assumed
512 tokens
Returns
Probability or score

Best app to run it on the Intel Arc A380

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf QuantFactory/shieldgemma-2b-GGUF:Q8_0
  • LM Studio Point-and-click: search, download and chat in one window.
  • Ollama Intel GPU support here is experimental (Vulkan).

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf QuantFactory/shieldgemma-2b-GGUF:Q8_0
  • LM Studio Point-and-click: search, download and chat in one window.
  • Ollama Intel GPU support here is experimental (Vulkan).

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 ShieldGemma 2B

Recommended for the Intel Arc A380: Q8_0. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run shieldgemma:2b

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q8_0 file (opens in a new tab)

huggingface.co/QuantFactory/shieldgemma-2b-GGUF (opens in a new tab)

ollama run hf.co/QuantFactory/shieldgemma-2b-GGUF:Q8_0

Original weights · Hugging Face

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

huggingface.co/google/shieldgemma-2b (opens in a new tab)

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

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

How it’s rated

Quality 58Good quality (B) · 58 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q8_0, 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 Runs well
How well it runs on the Intel Arc A380: 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.26.1 / 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.8.3 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.15.0 / 15
Match score74.4 / 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 A380

Quant Memory needed Available Time per decision Runs Quality Download
Q4_K_M 2.7 GB 6.0 GB 315 ms Runs well 55Good quality (B) · 55 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 3.0 GB 6.0 GB 318 ms Runs well 56Good quality (B) · 56 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 3.3 GB 6.0 GB 322 ms Runs well 57Good quality (B) · 57 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 3.9 GB 6.0 GB 330 ms Runs well 58Good quality (B) · 58 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 6.3 GB 6.0 GB 383 ms Runs welloffloads to RAM 58Good quality (B) · 58 of 100: how capable the model is at F16, whatever it runs on. Match score 58/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 1 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.