howtospark
models / Nanbeige/Nanbeige4.3-33B
?

33B paramsbfloat16GQA 56:8524K ctxapache-2.0
Sparks
Users
~81 GB
~65 GB
~48 GB
~32 GB
~25 GB
110 usable
Spec decode
Context33K / 524KKV
On the Sparks — 1× · 1-bit GGUF (dynamic) · 33K ctx · FP16 KV~434K ctx fits usable · ~13 users fit
spark
86 GB free
110 usable
25* / 110 GB
22% 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 layerstransformer layer
in
out
all 52 layers fire per token — 33.1B active
Optimize
Quantized from

Nanbeige/Nanbeige4.3-33B-Base

Analyze the original repo for the full architecture picture.

Verdict

33B params, ~66 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.1 tok/s ceiling; a trained EAGLE-style draft multiplies tokens per weight-read.

Tame the KV cache

At 524288 tokens the KV cache alone is ~112 GB at FP16; quantize or evict.

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.