Uploaded May 2026 | Updated September 2026, 3 weeks ago
One llama.cpp update just made Local AI 65% faster on a MacBook Pro — and 23% faster on a budget GPU using the exact same flag.
The feature is called Multi-Token Prediction (MTP), recently merged into llama.cpp. And depending on whether your setup is CPU-bound or GPU-bound, the speed gains can be massive.
In this video:
— What MTP / Multi-Token Prediction actually does
— Why Local AI inference suddenly got much faster
— MacBook Pro benchmarks (+65%)
— Budget GPU + MoE offload benchmarks (+23%)
— Why the same llama.cpp update behaves differently on different hardware
— Qwen 3.6 MTP GGUF testing
— ngram-mod speculative decoding explained
— Best llama.cpp flags for local LLM speed
The results:
• MacBook Pro (Metal, dense 27B): 1.65x speedup, 92.8% draft acceptance
• Budget GPU + MoE offload (35B-A3B): 1.23x speedup, 84.4% draft acceptance
Same model family. Same llama.cpp update. Completely different scaling behavior.
If you run Local AI, llama.cpp, Qwen, MoE models, or self-hosted LLMs — this update matters.
━━━━━━━━━━━━━━━━━━━━━━
🕒 CHAPTERS
━━━━━━━━━━━━━━━━━━━━━━
0:00 Local AI just got faster
0:44 What MTP actually does
1:54 MacBook Pro result — +65%
3:04 Budget GPU result — +23%
4:46 Why the gains split
6:28 ngram-mod speculative decoding
7:29 Best settings cheat sheet
━━━━━━━━━━━━━━━━━━━━━━
🔗 RESOURCES
━━━━━━━━━━━━━━━━━━━━━━
• llama.cpp PR #22673 (MTP merge)
github.com/ggml-org/llama.cpp/pull/22673
• Unsloth Qwen 3.6 27B MTP GGUF
huggingface.co/unsloth/Qwen3.6-27B-MTP-GGUF
• Unsloth Qwen 3.6 35B-A3B MTP GGUF
huggingface.co/unsloth/Qwen3.6-35B-A3B-MTP-GGUF
• Previous video: DFlash speculative decoding deep dive
━━━━━━━━━━━━━━━━━━━━━━
🟢 DISCORD
━━━━━━━━━━━━━━━━━━━━━━
Local AI, llama.cpp, homelab builds, weird inference experiments, low-VRAM setups.
If you're building ownership-first AI systems too:
discord.gg/XgBzczAWs
━━━━━━━━━━━━━━━━━━━━━━
I read llama.cpp draft PRs the day they land so you don’t have to.
Subscribe for:
• Local AI
• llama.cpp optimization
• MoE offload experiments
• low-VRAM inference
• self-hosted AI systems
• weird benchmark discoveries
#localai #llamacpp #mtp #qwen #speculativedecoding #ai
One llama.cpp update just made Local AI 65% faster on a MacBook Pro — and 23% faster on a budget GPU using the exact same flag.
The feature is called Multi-Token Prediction (MTP), recently merged into llama.cpp. And depending on whether your setup is CPU-bound or GPU-bound, the speed gains can be massive.
In this video:
— What MTP / Multi-Token Prediction actually does
— Why Local AI inference suddenly got much faster
— MacBook Pro benchmarks (+65%)
— Budget GPU + MoE offload benchmarks (+23%)
— Why the same llama.cpp update behaves differently on different hardware
— Qwen 3.6 MTP GGUF testing
— ngram-mod speculative decoding explained
— Best llama.cpp flags for local LLM speed
The results:
• MacBook Pro (Metal, dense 27B): 1.65x speedup, 92.8% draft acceptance
• Budget GPU + MoE offload (35B-A3B): 1.23x speedup, 84.4% draft acceptance
Same model family. Same llama.cpp update. Completely different scaling behavior.
If you run Local AI, llama.cpp, Qwen, MoE models, or self-hosted LLMs — this update matters.
━━━━━━━━━━━━━━━━━━━━━━
🕒 CHAPTERS
━━━━━━━━━━━━━━━━━━━━━━
0:00 Local AI just got faster
0:44 What MTP actually does
1:54 MacBook Pro result — +65%
3:04 Budget GPU result — +23%
4:46 Why the gains split
6:28 ngram-mod speculative decoding
7:29 Best settings cheat sheet
━━━━━━━━━━━━━━━━━━━━━━
🔗 RESOURCES
━━━━━━━━━━━━━━━━━━━━━━
• llama.cpp PR #22673 (MTP merge)
github.com/ggml-org/llama.cpp/pull/22673
• Unsloth Qwen 3.6 27B MTP GGUF
huggingface.co/unsloth/Qwen3.6-27B-MTP-GGUF
• Unsloth Qwen 3.6 35B-A3B MTP GGUF
huggingface.co/unsloth/Qwen3.6-35B-A3B-MTP-GGUF
• Previous video: DFlash speculative decoding deep dive
━━━━━━━━━━━━━━━━━━━━━━
🟢 DISCORD
━━━━━━━━━━━━━━━━━━━━━━
Local AI, llama.cpp, homelab builds, weird inference experiments, low-VRAM setups.
If you're building ownership-first AI systems too:
discord.gg/XgBzczAWs
━━━━━━━━━━━━━━━━━━━━━━
I read llama.cpp draft PRs the day they land so you don’t have to.
Subscribe for:
• Local AI
• llama.cpp optimization
• MoE offload experiments
• low-VRAM inference
• self-hosted AI systems
• weird benchmark discoveries
#localai #llamacpp #mtp #qwen #speculativedecoding #ai




![Can a 3.5GB model replace my 35B daily driver? (Bonsai 27B)
PrismML compressed Qwens 27B dense model down to 3.5 GB with true 1-bit weights. Not quantization: the weights were trained as −1/+1 from day one. So I put both Bonsai builds up against my actual daily driver, a 21 GB Qwen 3.6 35B MoE, plus Gemma 4 12B as the fair-size control, and ran about thirty tests on one RTX 3060.
Same landing-page brief. Same broken server over SSH. Same sampling settings, same KV cache quant, same effort level, every model.
What came out of it surprised me more than once. The 21 GB model is more than twice as fast as a 7 GB one, and the reason has nothing to do with file size. The only model that could not reliably finish a long task was not the smallest one. And whether Bonsai makes sense on your machine comes down to a number almost nobody quotes on a spec sheet.
If you run this on a Mac or a small card, tell me what you get in the comments.
CHAPTERS
0:00 Two models, one broken server
0:39 What Bonsai actually is (1-bit vs quantization)
3:24 Test 1 — can it design a webpage?
6:34 Test 2 — SSH debugging, everyone passed
9:26 Test 3 — the trap that survives a restart
13:29 Where it breaks (Gemmas loop)
15:35 Why the bigger model is faster (A3B vs dense)
17:54 The number nobody quotes (total footprint)
20:06 The verdict — who should run what
THE MODELS
Bonsai 27B (binary Q1_0, 3.5 GB / ternary Q2_0, 7 GB): [https://huggingface.co/prism-ml]
Qwen 3.6 35B-A3B: [https://huggingface.co/unsloth/Qwen3.6-35B-A3B-GGUF]
llama.cpp Metal Q2_0 support (merged): github.com/ggml-org/llama.cpp/pull/25419
llama.cpp CUDA Q2_0 support (open PR I built from): github.com/ggml-org/llama.cpp/pull/25707
THE RIG:
RTX 3060 12 GB
llama.cpp built from PR #25707
KV cache q8_0 (all models)
reasoning effort medium (all models)
MoE runs with 26 expert layers offloaded to system RAM
MY RESULTS AT A GLANCE
Generation speed at depth (tg, tokens/sec):
MoE 47.9 · Bonsai Q1 34.7 · Bonsai Q2 21.6
Total memory footprint:
MoE ~21 GB (10.5 VRAM + 10.6 RAM)
ternary 8.8 GB
binary 5.3 GB
Server-repair task, wall clock:
MoE ~56s
ternary ~114s
binary ~134s
Design test:
ternary and the MoE land in the same class.
Binary and Gemma sit a tier below.
#localai #llm #bonsai #quantization #1bit #qwen #llamacpp #selfhosted #ai #rtx3060 Can a 3.5GB model replace my 35B daily driver? (Bonsai 27B)](https://i.ytimg.com/vi/rBLWDJrXCp0/mqdefault.jpg)





