howtospark
models / unsloth/Muse-Glimmer-30B-GGUF
Meta logo

unsloth/Muse-Glimmer-30B-GGUF
28B paramsbfloat16GQA 32:2131K ctxmultimodalapache-2.0GGUF
Sparks
~65 GB
~52 GB
~38 GB
~24 GB
~18 GB
110 usable
Spec decode
Context33K / 131KKV
On the Sparks — 1× · 1-bit GGUF (dynamic) · 33K ctx · FP16 KV~1.8M ctx fits usable
spark
92 GB free
110 usable
18* / 110 GB
16% of usable
Dense weightsKV cacheActivations + graphsOS reserve

* segment sizes marked with an asterisk are estimates pending a measured run

Estimated per-node footprint, weights + KV sharded across the Spark (tensor parallel). Overhead ~8 GB/node; KV at FP16.

layer map
52 layerssliding window×39full attention×13
in
out
all 52 layers fire per token — 27.9B active
Optimize
Quantized from

meta-models/Muse-Glimmer-30B

Analyze the original repo for the full architecture picture.

Verdict

28B params, ~56 GB at bfloat16 — fits on one Spark as-is.

Make it fit

Get the weights (and headroom for KV) inside the 128 GB pool — the hard gate.

Lossless compression

BF16 weights entropy-code ~30% smaller bit-exact — smaller downloads and less bandwidth per token, no quality question at all.

Make it fast

Once it fits: fewer bytes per token and fewer decode steps against 273 GB/s.

Add a speculative decoder

Decode is bandwidth-bound at ~4.9 tok/s ceiling; a trained EAGLE-style draft multiplies tokens per weight-read.

Make it yours

Change what the model does — adapt, edit, or steer it — independent of size.

Fine-tune it

LoRA/QLoRA adapts behavior on one Spark without touching the base weights.