1-bit Bonsai 27B needs ~10.3 GB VRAM. Intel Arc A770 16GB has 16.0 GB. With Q1_0_G128 quantization, expect ~52 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
55.9 tok/s
TTFT
3465 ms
Safe context
157K
Memory
7.4 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 | 51.6 tok/s | 2047 ms | 39K |
| Coding | S | Runs well | 51.6 tok/s | 3754 ms | 39K |
| Agentic Coding | S | Tight fit | 51.6 tok/s | 5460 ms | 39K |
| Reasoning | S | Runs well | 51.6 tok/s | 4436 ms | 39K |
| RAG | S | Tight fit | 51.6 tok/s | 6825 ms | 39K |
Inference speed
Estimated decode speed (tokens/sec) for 1-bit Bonsai 27B at Q1_0_G128 across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~156 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? |
|---|---|---|---|---|
| 32 GB | Q1_0_G128 | 156.1 | Fits | |
RX 7900 XTX 24GB | 24 GB | Q1_0_G128 | 132.5 | Fits |
How 1-bit Bonsai 27B (27B params) fits at each quantization level on Intel Arc A770 16GB (16.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q1_0_G128 | 1.125 | 3.9 GB | Very Low | A84 |
Q2_0_G128 | 1.71 | 7.2 GB | Low | S87 |
Q2_KBest for your GPU |
Copy-paste commands to run 1-bit Bonsai 27B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "prism-ml/Bonsai-27B-gguf" \
--hf-file "Bonsai-27B-gguf-Q1_0_G128.gguf" \
-c 4096 -ngl 99Yes, Intel Arc A770 16GB can run 1-bit Bonsai 27B with a S grade (Runs well). Expected decode speed: 51.6 tok/s.
1-bit Bonsai 27B (27B parameters) requires approximately 10.3 GB of memory with Q1_0_G128 quantization.
The recommended quantization for 1-bit Bonsai 27B is Q1_0_G128, which balances quality and memory efficiency.
On Intel Arc A770 16GB, 1-bit Bonsai 27B achieves approximately 51.6 tokens per second decode speed with a time-to-first-token of 3754ms using Q1_0_G128 quantization.
For coding workloads, 1-bit Bonsai 27B on Intel Arc A770 16GB receives a S grade with 51.6 tok/s and 39K context.
On Intel Arc A770 16GB, 1-bit Bonsai 27B can safely use up to 39K 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/bonsai-27b-on-arc-a770-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
Mac Studio M3 Ultra 256GB |
| 256 GB |
| Q1_0_G128 |
| 123.5 |
| Fits |
MacBook Pro M4 Max 128GB | 128 GB | Q1_0_G128 | 122.1 | Fits |
MacBook Pro M4 Max 64GB | 64 GB | Q1_0_G128 | 122.1 | Fits |
Mac Studio M2 Ultra 128GB | 128 GB | Q1_0_G128 | 102.9 | Fits |
Mac Studio M1 Ultra 128GB | 128 GB | Q1_0_G128 | 97.6 | Fits |
| 24 GB | Q1_0_G128 | 89.7 | Fits |
| 24 GB | Q1_0_G128 | 87.4 | Fits |
| 16 GB | Q1_0_G128 | 86.1 | Fits |
MacBook Pro M4 Pro 48GB | 48 GB | Q1_0_G128 | 76.9 | Fits |
| 12 GB | Q1_0_G128 | 69.5 | Fits |
| 12 GB | Q1_0_G128 | 53.3 | Fits |
MacBook Pro M3 Max 64GB | 64 GB | Q1_0_G128 | 53.2 | Fits |
MacBook Pro M1 Max 64GB | 64 GB | Q1_0_G128 | 48.8 | Fits |
| 8 GB | Q1_0_G128 | 28.0 | Tight |
Estimates for single-stream decoding at Q1_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 |
| S86 |
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.