Only with CPU offload

Muse Glimmer 30B at Q4_K_M needs 17.5 GB but only 9.7 GB is addressable, so about 47% of the layers would stream from system RAM at roughly 60 GB/s. Expect around 4.1 tokens per second — usable for batch work, painful for chat.

53% on GPU 8K context Q4_K_M · 16.8 GB Apache 2.0 Released 10 Aug 2026 New this month Vision

Meta's first open weights since Llama 4: a dense 30B distilled from Muse Spark for always-on local agents. Two KV heads keep the cache small.

What hardware do I need for Muse Glimmer 30B? →

The VRAM budget

weights 16.8 GB
Weights 16.8 GB KV cache @ 8K 0.18 GB Runtime overhead 0.6 GB Over budget 7.8 GB past 9.7 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
Q8_0 29.5 GB 30.3 GB ~1.7 −0.1% ppl 20.6 GB over
Q6_K 22.8 GB 23.5 GB ~2.4 −0.4% ppl 13.8 GB over
Q5_K_M 19.7 GB 20.4 GB ~3.1 −0.8% ppl 10.7 GB over
Q4_K_M 16.8 GB 17.5 GB ~4.1 −1.9% ppl 7.8 GB over
Q3_K_M 13.6 GB 14.3 GB ~6.3 −5.4% ppl 4.6 GB over
Q2_K 11.6 GB 12.4 GB ~9.5 −15% ppl 2.7 GB over

Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. This model interleaves sliding-window layers (2048 tokens, 13 of 52 layers global), which is why its cache barely grows with context.

How to run it

terminal
$ llama-server \
    -hf meta-models/Muse-Glimmer-30B:Q4_K_M \
    -c 8192 -ngl 27

The engine underneath most of the others. Every knob is exposed. More on llama.cpp.

01Download is 16.8 GB. Keep it on an SSD — a first load off a spinning disk takes minutes.
02Close anything else holding VRAM. A browser with hardware acceleration can sit on 1–2 GB.
03If it falls back to CPU silently, drop the context first, then step down a quantisation.
See all models for this rig Compare with another model