No — not on this device
Muse Glimmer 30B at Q4_K_M needs 17.5 GB against 10.7 GB usable, and the shortfall of 6.8 GB is more than 128 GB of system RAM can cover at a tolerable speed. A smaller sibling or a lower quantisation is the honest answer here.
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.
The VRAM budget
Quantisation ladder
| Quant | Weights | Total @ 8K | Max context | Tok/s | Quality | Fit |
|---|---|---|---|---|---|---|
| Q8_0 | 29.5 GB | 30.3 GB | — | ~1.3 | −0.1% ppl | 19.6 GB over |
| Q6_K | 22.8 GB | 23.5 GB | — | ~1.7 | −0.4% ppl | 12.8 GB over |
| Q5_K_M | 19.7 GB | 20.4 GB | — | ~1.9 | −0.8% ppl | 9.7 GB over |
| Q4_K_M | 16.8 GB | 17.5 GB | — | ~2.3 | −1.9% ppl | 6.8 GB over |
| Q3_K_M | 13.6 GB | 14.3 GB | — | ~2.8 | −5.4% ppl | 3.6 GB over |
| Q2_K | 11.6 GB | 12.4 GB | — | ~3.3 | −15% ppl | 1.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
$ pip install mlx-lm $ mlx_lm.generate --model mlx-community/Muse-Glimmer-30B-4bit \ --max-tokens 512 --prompt "Hello"
Apple's own array framework. The fastest path on Apple Silicon. More on MLX.