on

Can the Intel Arc A380 run Muse Glimmer 30B?

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

Yes, but slowly (heavy RAM offload)

Slow (heavy RAM offload). At Q4_K_M it needs about 19.2 GB of 6.0 GB usable, with an estimated speed of 3.2 tok/s.

Best quant
Q4_K_M
Generation speed
3.2 tok/s
Prompt processing
74.6 tok/s
First token (1K prompt)
13.7 s
Largest safe context
—

Best app to run it on the Intel Arc A380

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Splits the model between GPU memory and system RAM, which this setup needs.
  • Gives you direct control of how many layers sit on the GPU, the best way to squeeze a model that doesn’t quite fit.
  • Supports Intel Arc through SYCL and Vulkan.
llama-server -hf meta-models/Muse-Glimmer-30B-GGUF:Q4_K_M
  • LM Studio Splits the model between GPU memory and system RAM, which this setup needs.
  • Ollama Splits the model between GPU memory and system RAM, which this setup needs.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Splits the model between GPU memory and system RAM, which this setup needs.
  • Gives you direct control of how many layers sit on the GPU, the best way to squeeze a model that doesn’t quite fit.
  • Supports Intel Arc through SYCL and Vulkan.
llama-server -hf meta-models/Muse-Glimmer-30B-GGUF:Q4_K_M
  • LM Studio Splits the model between GPU memory and system RAM, which this setup needs.
  • Ollama Splits the model between GPU memory and system RAM, which this setup needs.

Want an agent? Muse Glimmer 30B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

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 Muse Glimmer 30B

Recommended for the Intel Arc A380: Q4_K_M. 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 muse-glimmer:30b-q4_K_M

Quantized files · GGUF

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

Download the Q4_K_M file (opens in a new tab)

huggingface.co/meta-models/Muse-Glimmer-30B-GGUF (opens in a new tab)

ollama run hf.co/meta-models/Muse-Glimmer-30B-GGUF:Q4_K_M

Original weights · Hugging Face

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

huggingface.co/meta-models/Muse-Glimmer-30B (opens in a new tab)

No sign-in needed.

How it’s rated

Quality 87Excellent quality (A+) · 87 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 62/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: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Slowheavy RAM offload
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.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.39.3 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.4.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.4.3 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score62.6 / 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 Speed Runs Quality Download
Q2_K 12.9 GB 6.0 GB 5.8 tok/s Slowheavy RAM offload 64Good quality (B) · 64 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 15.6 GB 6.0 GB 4.3 tok/s Slowheavy RAM offload 77Great quality (A) · 77 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 19.2 GB 6.0 GB 3.2 tok/s Slowheavy RAM offload 87Excellent quality (A+) · 87 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 22.2 GB 6.0 GB — Won't run 89Excellent quality (A+) · 89 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 25.4 GB 6.0 GB — Won't run 91Excellent quality (A+) · 91 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 32.6 GB 6.0 GB — Won't run 92Excellent quality (A+) · 92 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking.
F16 60.6 GB 6.0 GB — Won't run 92Excellent quality (A+) · 92 of 100: how capable the model is at F16, whatever it runs on. Match score 12/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

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.

Was this page helpful?