Ternary-Bonsai-2-27B-mlx-2bit

<p align="center"> <img src="./assets/bonsai-logo.svg" width="280" alt="Bonsai"> </p> <p align="center"> <a href="https://prismml.com"><b>Prism ML Website</b></a> &nbsp;|&nbsp; <a href="https://github.com/PrismML-Eng/Bonsai-demo/blob/main/bonsai-2-27b-whitepaper.pdf"><b>Whitepaper</b></a> &nbsp;|&nbsp; <a href="https://github.com/PrismML-Eng/Bonsai-demo"><b>Demo &amp; Examples</b></a> &nbsp;|&nbsp; <a href="https://discord.gg/prismml"><b>Discord</b></a> </p>

Bonsai 2 27B

Full 27B-class reasoning in ternary transformer weights — on everyday laptops

8.60 GB on disk, language model + vision tower | 98.2% of FP16 intelligence retained | ~47 tok/s on an Apple M5 Max laptop

Highlights

• 8.60 GB on disk: a 7.67 GB language model (down from ~54 GB FP16) plus the 0.92 GB vision tower. MLX's container stores a scale and a bias per group, so the language model costs 2.25 bits/weight where the same ternary weights take 1.75 in the GGUF PTQ1_0 packing
• 98.2% of FP16 intelligence retained: 84.78 average across 14 thinking-mode benchmarks — far above the conventional IQ2_XXS build (72.59) at less than two-thirds 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, with no high-precision escape hatches behind a low-bit label — a true 1.72 bits per weight as a representation, 2.25 as MLX stores it; the vision tower is bundled in this pack, unquantized
• 262K-token context on-device, kept practical by the Qwen3.8-27B hybrid-attention backbone (~75% linear attention)
• Custom ternary hybrid-attention kernels on Apple MLX (Python, Swift) and CUDA — packed weights are consumed directly, never expanded back to FP16
• GGUF companion: also available as Ternary-Bonsai-2-27B-gguf for llama.cpp (CUDA, Metal, CPU), in two packings — PTQ1_0 (5.95 GB) and PQ2_0 (7.21 GB)

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: MLX fork (Apple Silicon) · mlx-swift fork (iOS/macOS) · llama.cpp fork (CUDA)
• 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

Those are language-model figures; the pack on disk is 8.60 GB once the 0.92 GB vision tower is included.

Practical deployment needs packing formats that efficient kernels can consume, and Bonsai 2 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. 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.

Unlike conventional low-bit builds — whose advertised labels understate their true average bit-width (a widely-used "2-bit" build of Qwen3.8-27B is really 2.8 bits/weight at 9.4 GB) — the Bonsai representation carries a bit-width that matches its name.

MLX Packaging

This pack carries both the language model and the vision tower. model.safetensors is 8.60 GB: 7.67 GB of packed language weights and 0.92 GB for the tower, which is the official Qwen3.8-27B vision tower carried unrotated and unquantized in FP16. The Hadamard rotation applies only to the language model's projections, so the tower needs no transform and is plain passthrough.

MLX's grouped low-bit format stores both a scale and a bias per group. The ternary levels {-s, 0, +s} are reproduced exactly by setting scale = s and bias = -s, so the 2-bit codes {0, 1, 2} decode to -s, 0, +s. The bias carries no new information, but the container stores two FP16 values per group of 128 where the native format stores one. The effective rate is therefore 2.25 bits/weight against PQ2_0's 2.13. This is a container property, not a different representation: the packed weights decode to exactly the same ternary values as the GGUF bands, verified by comparing the group scales bit for bit.

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.0, 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

These match the base model's own generation_config.json and are the values carried in the GGUF metadata (general.sampling.*), so a client that reads model defaults will use them without being told. They are also the settings used for the reported benchmark results (thinking mode).

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

Quickstart

PrismML-Eng/Bonsai-demo is the source of truth for running these models. It carries the tested setup, builds the right MLX runtime, and is kept current. Where anything here disagrees with it, it is right.

hf download prism-ml/Ternary-Bonsai-2-27B-mlx-2bit --local-dir bonsai2-27b-mlx

This pack declares model_type: prism_hadamard_qwen35 and requires the loader bundled in runtime/. Ordinary MLX loaders skip the activation transform and the inverse embedding lookup, so they return wrong output rather than an error.

pip install -r bonsai2-27b-mlx/runtime/requirements.txt

import sys
sys.path.insert(0, "bonsai2-27b-mlx/runtime")
from vision_artifact import load_vl_model, chat_config
from mlx_vlm import generate
from mlx_vlm.prompt_utils import apply_chat_template

model, processor, config = load_vl_model("bonsai2-27b-mlx")
prompt = apply_chat_template(processor, chat_config(config), "What is in this image?", num_images=1)
print(generate(model, processor, prompt, ["photo.jpg"], max_tokens=256, temperature=1.0))

Pass no images for text-only use. chat_config is needed because mlx-vlm's prompt helper keys off model_type. Everything runs on stock packages, no fork; PACK-RUNTIME.md documents the contract and Bonsai-demo carries the tested setup.

For CUDA, CPU, and llama.cpp on Metal, use the GGUF packs of the same weights: Ternary-Bonsai-2-27B-gguf. Those need a build of our llama.cpp fork; stock llama.cpp cannot run them.

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. Rows are measured with llama.cpp (Metal/CUDA, custom low-bit kernels) on the GGUF packs of the same weights, 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.9 GB, Bonsai 2 27B outscores the sub-4-bit conventional build by more than twelve points at less than two-thirds 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

<details> <summary>Expand full per-benchmark results (thinking mode)</summary> </details>

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 over 2.3x the density of the densest conventional build (IQ2_XXS at 0.199) and nearly 9x FP16 — no conventional build of Qwen3.8-27B exceeds 0.2. Each stored gigabyte is translated into far more usable intelligence. Against the previous Bonsai 27B release, density rises from 0.416 to 0.469, a 12.5% 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; deployments that need the last few points of accuracy can still reach for the full-precision model where its footprint is not a constraint
• 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: [email protected]