Ternary Bonsai 27B needs ~13.6 GB VRAM. Intel Arc Pro B50 16GB has 16.0 GB. With Q2_0_G128 quantization, expect ~12 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
Runs well
Decode
13.1 tok/s
TTFT
14793 ms
Safe context
103K
Memory
10.7 GB / 16.0 GB
The raw memory story may look fine, but the software ecosystem is still a constraint here.
Runtime ecosystem is narrower than CUDA
Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.
Prefer CUDA if you want the path of least resistance
If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | S | Runs well | 12.1 tok/s | 8741 ms | 26K |
| Coding | A | Tight fit | 12.1 tok/s | 16026 ms | 26K |
| Agentic Coding | A | Very compromised | 7.7 tok/s | 36689 ms | 26K |
| Reasoning | A | Tight fit | 12.1 tok/s | 18940 ms | 26K |
| RAG | A | Very compromised | 7.7 tok/s | 45862 ms | 26K |
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 Intel Arc Pro B50 16GB (16.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q1_0_G128 | 1.125 | 3.9 GB | Very Low | S86 |
Q2_0_G128 | 1.71 | 7.2 GB | Low | S89 |
Q2_KBest for your GPU |
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, Intel Arc Pro B50 16GB can run Ternary Bonsai 27B with a A grade (Tight fit). Expected decode speed: 12.1 tok/s.
Ternary Bonsai 27B (27B parameters) requires approximately 13.6 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 Intel Arc Pro B50 16GB, Ternary Bonsai 27B achieves approximately 12.1 tokens per second decode speed with a time-to-first-token of 16026ms using Q2_0_G128 quantization.
For coding workloads, Ternary Bonsai 27B on Intel Arc Pro B50 16GB receives a A grade with 12.1 tok/s and 26K context.
On Intel Arc Pro B50 16GB, Ternary Bonsai 27B can safely use up to 26K 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-arc-pro-b50-16gb" 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.
| 2 |
10.5 GB |
| Low |
| S88 |
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 |
Prefer CUDA if you want the path of least resistance. If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.
Often yes, if your goal is the easiest setup and the widest runtime support. Intel can offer attractive memory capacity, but CUDA still tends to win on tooling maturity, guides, kernels, and model coverage for local AI.