prism-ml · text

Ternary-Bonsai-1.7B-unpacked

prism-ml/Ternary-Bonsai-1.7B-unpacked

Ternary-Bonsai-1.7B-unpacked at Q2_0 is exactly 463,290,464 bytes (0.43 GiB / 0.46 GB) — an effective 2.155 bits per weight, not the nominal 2. Its KV cache at 32K is 3.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
1.7B
Architecture
qwen3
28 layers
Context
32,768
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q2_00.43 GiB463,290,4642.155prism-ml
F163.21 GiB3,446,249,40816.029prism-ml

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.44 GiB0.44 GiB28 / 0 / 0
8,1920.88 GiB0.88 GiB28 / 0 / 0
16,3841.75 GiB1.75 GiB28 / 0 / 0
32,7683.50 GiB3.50 GiB28 / 0 / 0
65,5367.00 GiB7.00 GiB28 / 0 / 0
131,07214.00 GiB14.00 GiB28 / 0 / 0

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q2_0 at roughly 0.90 GiB. The real file is 0.43 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
28
Attention heads
16
KV heads
8
Head dim
128
Hidden size
2048
Vocab
151,669
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window
false

Questions people ask

How much VRAM does Ternary-Bonsai-1.7B-unpacked need?
Q2_0 is exactly 463,290,464 bytes (0.43 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Ternary-Bonsai-1.7B-unpacked's KV cache?
3.50 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of Ternary-Bonsai-1.7B-unpacked should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.