Ternary Bonsai 27B needs ~13.1 GB VRAM. RTX 2080 Ti 11GB has 11.0 GB. With Q2_0_G128 quantization, expect ~20 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
Fit status
Tight fit
Decode
43.3 tok/s
TTFT
4469 ms
Safe context
29K
Memory
10.2 GB / 11.0 GB
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 20% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
Older PCIe generation
PCIe 3.0 is workable, but it compounds the penalty when you offload heavily or try to scale across multiple cards.
Remove offload with more accelerator memory
Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Increase host RAM if you keep offloading
This setup may need roughly {ram} GB of extra host RAM just for the offloaded portion, before OS and other tools.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | S | Runs with offload | 28.2 tok/s | 3739 ms | 7K |
| Coding | A | Very compromised | 19.8 tok/s | 9767 ms | 7K |
| Agentic Coding | F | Too heavy | 11.2 tok/s | 25183 ms | 7K |
| Reasoning | A | Very compromised | 19.8 tok/s | 11542 ms | 7K |
| RAG | F | Too heavy | 11.2 tok/s | 31478 ms | 7K |
Inference speed
Estimated decode speed (tokens/sec) for Ternary Bonsai 27B at Q2_0_G128 across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 4080 Super 16GB at ~87 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.
| GPU / Mac | Memory | Quant | Speed (tok/s) | Fits? |
|---|---|---|---|---|
| 16 GB | Q2_0_G128 | 87.2 | Fits | |
| 32 GB | Q2_0_G128 | 76.2 | Fits | |
How Ternary Bonsai 27B (27B params) fits at each quantization level on RTX 2080 Ti 11GB (11.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q1_0_G128 | 1.125 | 3.9 GB | Very Low | S90 |
Q2_0_G128Best for your GPU | 1.71 | 7.2 GB | Low | S89 |
Copy-paste commands to run Ternary Bonsai 27B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "prism-ml/Ternary-Bonsai-27B-gguf" \
--hf-file "Ternary-Bonsai-27B-gguf-Q2_0_G128.gguf" \
-c 4096 -ngl 99Yes, RTX 2080 Ti 11GB can run Ternary Bonsai 27B with a A grade (Very compromised). Expected decode speed: 19.8 tok/s.
Ternary Bonsai 27B (27B parameters) requires approximately 13.1 GB of memory with Q2_0_G128 quantization.
The recommended quantization for Ternary Bonsai 27B is Q2_0_G128, which balances quality and memory efficiency.
On RTX 2080 Ti 11GB, Ternary Bonsai 27B achieves approximately 19.8 tokens per second decode speed with a time-to-first-token of 9767ms using Q2_0_G128 quantization.
For coding workloads, Ternary Bonsai 27B on RTX 2080 Ti 11GB receives a A grade with 19.8 tok/s and 7K context.
On RTX 2080 Ti 11GB, Ternary Bonsai 27B can safely use up to 7K tokens of context. The model's official context limit is 262K, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/ternary-bonsai-27b-on-rtx-2080-ti-11gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| 24 GB |
| Q2_0_G128 |
| 64.6 |
| Fits |
Mac Studio M3 Ultra 256GB | 256 GB | Q2_0_G128 | 60.3 | Fits |
MacBook Pro M4 Max 128GB | 128 GB | Q2_0_G128 | 59.6 | Fits |
MacBook Pro M4 Max 64GB | 64 GB | Q2_0_G128 | 59.6 | Fits |
Mac Studio M2 Ultra 128GB | 128 GB | Q2_0_G128 | 50.2 | Fits |
Mac Studio M1 Ultra 128GB | 128 GB | Q2_0_G128 | 47.6 | Fits |
| 24 GB | Q2_0_G128 | 43.8 | Fits |
| 24 GB | Q2_0_G128 | 42.6 | Fits |
MacBook Pro M4 Pro 48GB | 48 GB | Q2_0_G128 | 37.5 | Fits |
| 12 GB | Q2_0_G128 | 26.0 | Tight |
MacBook Pro M3 Max 64GB | 64 GB | Q2_0_G128 | 26.0 | Fits |
MacBook Pro M1 Max 64GB | 64 GB | Q2_0_G128 | 23.8 | Fits |
| 12 GB | Q2_0_G128 | 17.5 | Tight |
| 8 GB | Q2_0_G128 | 6.6 | Too big |
Estimates for single-stream decoding at Q2_0_G128; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.
Q2_K |
| 2 |
10.5 GB |
| Low |
| F0 |
Q3_K_S | 3 | 13.2 GB | Low | F0 |
NVFP4 | 4 | 15.1 GB | Medium | F0 |
Q4_K_M | 4 | 16.5 GB | Medium | F0 |
Q5_K_M | 5 | 19.4 GB | High | F0 |
Q6_K | 6 | 22.1 GB | High | F0 |
Q8_0 | 8 | 28.9 GB | Very High | F0 |
F16 | 16 | 55.4 GB | Maximum | F0 |
Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.