Prism ML Website  |  Whitepaper  |  Demo & Examples  |  Discord

Bonsai 2 27B — GGUF

Full 27B-class reasoning in ternary transformer weights, for llama.cpp (CUDA, Metal, CPU)

~9.3x smaller than FP16 (ideal) | 98.2% of FP16 intelligence retained | ~47 tok/s on an Apple M5 Max laptop

Highlights

• ~5.9 GB language model (down from ~54 GB FP16) — full 27B-class reasoning on a standard laptop or a single GPU
• 98.2% of FP16 intelligence retained: 84.78 average across 14 thinking-mode benchmarks — far above the conventional IQ2_XXS build (72.59) at about 82% of its footprint, and within 0.4 points of UD-Q4_K_XL at three times the footprint
• Retains thinking, reasoning, and agentic behavior deep in the sub-4-bit regime, where conventional low-bit representations collapse: math within half a point of full precision (96.57), coding level with the baseline (89.42), agentic tool calling at 74.92
• End-to-end ternary language weights across embeddings, attention projections, MLP projections, and LM head, at a true 1.72 bits per weight — no high-precision escape hatches behind a low-bit label; the vision tower ships as a separate Q8_0 mmproj pack
• 262K-token context on-device, kept practical by the Qwen3.8-27B hybrid-attention backbone (~75% linear attention)
• Two GGUF packings with custom ternary hybrid-attention kernels for llama.cpp (CUDA, Metal) — PTQ1_0 packs trits densely (1.75 bits/weight, 5.95 GB), PQ2_0 stores each trit in a 2-bit slot (2.13 bits/weight, 7.21 GB); packed weights are consumed directly, never expanded back to FP16
• Runs on stock llama.cpp too: a Q2_0 packing (2.25 bits/weight, 7.63 GB) runs in mainline llama.cpp from release b11556 onward, no fork needed
• MLX companion: also available as Ternary-Bonsai-2-27B-mlx-2bit for native Apple Silicon inference

Resources

• Whitepaper — full methodology, benchmarks, and measurement notes
• Demo & examples — the source of truth for running these models: tested setup for every backend, pinned binaries, serving, benchmarking and integration, kept current as the runtimes move
• Low-bit kernels: llama.cpp fork (CUDA + Metal) · MLX fork (Apple Silicon) · mlx-swift fork (iOS/macOS)
• Known issues — problems we know about, with workarounds and fix status
• Discord — join the community for support, discussion, and updates

Model Overview

Weight Representation: Ternary g128

Each weight takes a value from {−1, 0, +1}, with one shared FP16 scale factor for every group of 128 weights. A ternary value carries log₂3 ≈ 1.585 bits of information, so the effective storage cost of the format is ~1.71 bits/weight (ternary code + 16-bit scale amortized over 128 weights); counting the small set of tensors held above the ternary representation brings the model as a whole to 1.72 bits/weight — an idealized ~9.3x reduction vs FP16.

The weights are stored in a rotated basis: each matrix is transformed blockwise by an orthogonal Hadamard rotation before the ternary assignment, and the runtime applies the matching transform to activations. The rotation is folded into the stored weights offline, so it costs no extra bits and no extra weight traffic; the packed model declares its rotation as metadata, so a runtime either applies the matching transform or refuses to load the file.

Memory Requirement

Practical deployment needs packing formats that efficient kernels can consume, and this repo ships two: PTQ1_0 packs trits densely and lands essentially on the information-theoretic target, while PQ2_0 stores each trit in a 2-bit slot, trading footprint for cheaper unpacking. Neither is uniformly faster — see the throughput table below for where each wins. A third file, Q2_0, uses llama.cpp's standard 2-bit type instead, so stock llama.cpp can run it, at a somewhat larger size. These sizes describe the language model alone, the only component that must stay resident for text inference; 26.2M parameters (0.0976% of the language model — the recurrent state path of the linear-attention layers, plus the normalization weights) remain in higher precision and are counted in the 1.72 figure.

Shipped Components

The vision tower ships alongside the language model as an optional component (on-disk sizes):

The Q8_0 file carries the vision tower in an 8-bit container. It is usually offloaded, loaded only when an image actually arrives, so text-only serving never pays for it.

Best Practices

Generation Parameters

We recommend using the following sets of sampling parameters for generation:

• Thinking Mode: temperature=1.0, top_p=0.95, top_k=20, min_p=0.05, presence_penalty=0.0, repetition_penalty=1.0
• Instruct (or non-thinking) mode: temperature=0.7, top_p=0.80, top_k=20, min_p=0.0, presence_penalty=1.5, repetition_penalty=1.0

min_p=0.05 drops tokens far less likely than the top choice. In our tests it scored at least as well as min_p=0.0 and followed instructions more reliably, so we recommend it for thinking mode. It is also llama.cpp's default: the GGUF files carry top_k, top_p and temperature (general.sampling.*) but not min_p, so llama.cpp applies 0.05 without being told. The other values match the base model's own generation_config.json. The reported benchmark results were measured with the same settings, except min_p=0.0.

The model uses xhigh reasoning effort by default; use medium for shorter responses and a balance of speed and accuracy. low reasoning effort is not supported and when selected the model will behave close to xhigh.

System Prompt

You can use a simple system prompt such as:

You are a helpful assistant

Choosing a Packing

PQ2_0 is the faster decode on H100, A100, and the Blackwell cards, is faster at prompt processing everywhere, and is the pack measured on Apple Silicon. PTQ1_0 is the faster decode on the Ada-generation cards and the L4, and is the pick wherever memory is tightest. See the throughput table below.

Quickstart

PrismML-Eng/Bonsai-demo is the source of truth for running these models. It carries the tested setup for every backend, pins a known-good binary release, and is kept current as the kernels move. Where anything here disagrees with it, it is right.

Which llama.cpp runs which file

PQ2_0 and PTQ1_0 need the ternary hybrid-attention kernels in the PrismML-Eng/llama.cpp fork. Stock llama.cpp rejects them as unknown types. Use a binary from the fork.

Q2_0 runs on stock llama.cpp from release b11556 onward, which added the Hadamard activation runtime these weights need. Older stock builds load Q2_0 without any warning and produce garbage, so check your build first (llama-cli --version). Apps that bundle their own llama.cpp need an engine built from b11556 or newer.

# prebuilt, pick the archive for your platform
# https://github.com/PrismML-Eng/llama.cpp/releases/latest
tar -xzf llama-<tag>-bin-<platform>.tar.gz -C bin --strip-components=1

# or build it
git clone https://github.com/PrismML-Eng/llama.cpp && cd llama.cpp
cmake -B build -DGGML_CUDA=ON && cmake --build build -j    # drop -DGGML_CUDA=ON on macOS, Metal is default

hf download prism-ml/Ternary-Bonsai-2-27B-gguf Ternary-Bonsai-2-27B-PQ2_0.gguf --local-dir .

./bin/llama-cli -m Ternary-Bonsai-2-27B-PQ2_0.gguf \
    -ngl 99 -fa on -c 32768 \
    --temp 1.0 --top-p 0.95 --top-k 20 --min-p 0.05 \
    -p "Explain quantum computing in simple terms." -n 16384

With stock llama.cpp (b11556 or newer), use the Q2_0 file and the same flags:

hf download prism-ml/Ternary-Bonsai-2-27B-gguf Ternary-Bonsai-2-27B-Q2_0.gguf --local-dir .
llama-cli -m Ternary-Bonsai-2-27B-Q2_0.gguf \
    -ngl 99 -fa on -c 32768 \
    --temp 1.0 --top-p 0.95 --top-k 20 --min-p 0.05 \
    -p "Explain quantum computing in simple terms." -n 16384

The binary is ./bin/llama-cli from an extracted release archive, or ./build/bin/llama-cli if you built the fork yourself. -ngl 99 offloads every layer, 0 is CPU-only; -c sets the context, up to 262144. -n 16384 leaves room for the thinking trace: the template defaults to xhigh reasoning effort, so a small cap such as 256 tokens ends generation mid-thought, before any answer. --min-p 0.05 is llama.cpp's default; it is written out so the command states every recommended setting.

This is a reasoning model and it thinks by default. For the server, tool calling, reasoning budgets, image input with the mmproj file, and speculative decoding, follow Bonsai-demo, which ships run scripts that pick the right flags for your hardware.

Cross-Platform Throughput

tg128 is token-generation throughput over 128 generated tokens (the memory-bandwidth-bound, interactive phase); pp512 is prompt-processing throughput over 512 input tokens (the compute-bound phase). Both in tokens/s, measured with llama-bench on these GGUF packs (custom low-bit kernels), at batch size 1 and depth 0 with no vision tower. NVIDIA energy is board power including HBM/GDDR.

On the laptop the FP16 baseline (~54 GB) does not fit at all — the meaningful statement is not a speedup ratio but that a 27B model runs interactively on an everyday laptop. The measured decode streams ~204 GB/s of weights on the M5 Pro, confirming the memory-bandwidth-dominated profile that the low-bit representation is built to exploit. The M5 Pro figure is measured on a quiet machine; this laptop swings ~4% with background load.

The two packings are a genuine trade rather than a strict ordering. PTQ1_0 moves 17% less weight data per step, but unpacking dense trits costs arithmetic, so it wins on the Ada-generation parts and the L4 — where memory is the binding constraint — and loses on H100, A100, and the Blackwell cards, where batch-1 decode is limited by instruction throughput and launch overhead instead. Prompt processing, being compute-bound, favors PQ2_0 everywhere.

The Apple row carries no per-token energy figure because the two platforms' instrumentation does not enclose the same components: nvidia-smi includes the card's HBM/GDDR, while Apple's powermetrics reports CPU, GPU, and ANE with no DRAM rail. What the measurement does support is absolute draw: the M5 Pro decodes at 27.5 W on the GPU rail and 34.1 W across CPU and GPU, against 300–455 W of board power for the NVIDIA cards above.

Additional Apple Platforms

Measured on the earlier pre-rotation build and reported pending re-measurement on the current stack (llama.cpp Metal backend):

On the wider M5 Max the model reaches ~47 tok/s; on the M4 Pro, prefill (~125 tok/s) rather than decode is the practical limit for very long prompts.

Benchmarks

Evaluated with EvalScope + vLLM on NVIDIA H100 under identical infrastructure, decoding, and scoring, in thinking mode — where the model's full reasoning is exercised and the sub-4-bit collapse of conventional methods is most visible. 14 benchmarks across six skill categories. Bit-widths are true averages; "vs FP16" is relative to the Qwen3.8-27B FP16 reference.

At 5.95 GB, Bonsai 2 27B outscores the sub-4-bit conventional build by more than twelve points at about 82% of its size, and comes within 0.4 points of UD-Q4_K_XL at a third of its footprint.

The aggregate gap also understates how the conventional builds fail: their degradation is selective, concentrated on the benchmarks that demand sustained chains of reasoning. IQ2_XXS falls to 57.5 on AIME26 and 56.4 on LiveCodeBench while still scoring 88.93 on MMLU-Redux — which is why casual testing misses the collapse. Bonsai 2 holds exactly these benchmarks, scoring 95.83 and 90.07. The previous Bonsai 27B report showed the same pattern on a second model family, Gemma-4-31B, so the collapse is a property of the methods rather than of one base model.

By Skill Category

The reasoning backbone comes through intact: math falls only from 97.06 to 96.57, coding is level with the baseline, and instruction following is slightly ahead of it. The remaining gap is concentrated in the most demanding categories — knowledge and reasoning, and vision.

Full Per-Benchmark Results

Expand full per-benchmark results (thinking mode)

Intelligence Density

Intelligence density captures the ratio of a model's capability to its deployed size:

D = -log2(1 - score/100) / size_GB

Bonsai 2 27B delivers about 1.8x the density of the densest conventional build here (IQ2_XXS at 0.257) and nearly 9x FP16. Each stored gigabyte is translated into far more usable intelligence. For Bonsai 2 27B and the conventional builds, sizes are the on-disk sizes of the published files. Against the previous Bonsai 27B release, density rises from 0.416 to 0.457, a 9.9% gain; that row is recomputed on these same 14 benchmarks for a like-for-like comparison.

Use Cases

• Laptop-local 27B agents: full 27B reasoning and tool use on a standard laptop at ~28 tok/s, with the 262K context available for long-document analysis, full-repository code work, and other tasks that depend on holding a large working set in context
• Privacy-sensitive and offline settings: on-device execution keeps prompts and data on the device by construction, and works with intermittent or no connectivity
• Single-GPU and commodity-GPU serving: 27B-class quality from a single consumer or entry-level datacenter GPU — ~130 tok/s on an RTX 5090, ~30 tok/s on a 72 W L4 — with headroom for larger batches, longer contexts, or co-resident models
• Quality-first low-bit deployment: 98.2% of the full-precision model's benchmark average at roughly a ninth of its size

Limitations

• The quality–footprint trade-off: the ternary model retains 98.2% of the full-precision average, and the gap is modest and predictable — the reasoning core (math, coding) stays within a few points of baseline, with the difference concentrated in the most demanding categories
• Native low-bit kernels: the dense PTQ1_0 packing (1.75 bits/weight, 5.95 GB) now exists, but unpacking trits costs arithmetic — it is faster on Ada-class and smaller accelerators and slower on Ampere, Hopper, and Blackwell, where batch-1 decode is not bandwidth-starved; returning the footprint advantage as latency on every target is an active engineering target

Citation

If you use Bonsai 2 27B, please cite:

@techreport{bonsai2_27b,
    title   = {Bonsai 2 27B: A 27B Ternary Reasoning Model},
    author  = {Prism ML},
    year    = {2026},
    month   = {September},
    url     = {https://prismml.com}
}

Contact

For questions, feedback, or collaboration inquiries: contact@prismml.com