@analogalok: Run Gemma 4 26B MoE on 8GB VRAM with 250k context at 20+ tokens/sec If you own any 8GB VRAM graphics card, stop what yo…

X AI KOLs Timeline Tools

Summary

Alok demonstrates running Gemma 4 26B MoE on 8GB VRAM using Unsloth's QAT quant and the -cmoe flag in llama.cpp, achieving 20 tokens/sec with 250k context, marking a major milestone for budget local AI.

Run Gemma 4 26B MoE on 8GB VRAM with 250k context at 20+ tokens/sec If you own any 8GB VRAM graphics card, stop what you are doing. Local AI just had its absolute "Holy Shit" moment for budget hardware. Yesterday, I benchmarked Unsloth Gemma 4 12B Q4_K_XL on an 8GB card. The community went wild but immediately demanded more: "Can we run a 25B+ model on budget GPUs?" Today, I’m delivering exactly that. I am running a massive 26B parameter Mixture of Experts (MoE) model locally on a standard 8GB VRAM setup with 250k full native context!. If you own an RTX 3060, 3070, 4060, or any budget GPU with 8GB of VRAM, the local AI paradigm has completely changed. The performance metrics are astonishing: - 20 tokens/sec flat decode throughput. - Stable, flat decode speed even with massive prompts. - I threw a 60k token prompt at it, and it still clocked in at 20 TPS without dropping a single frame. # What about prefill? Yes, Time To First Token (TTFT) is slightly high when swallowing massive contexts. But with a solid 200 tokens/sec prefill speed, the wait is barely noticeable and highly usable. And this is running completely without Multi Token Prediction (MTP) active. How is this possible? It’s the magic of Google's new QAT (Quantization Aware Training) quants for Gemma 4. The model weight file (unsloth gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf) is only 13.2 GB, making it the ultimate local powerhouse. # The Test Setup: CPU: Intel Core i7 RAM: 16GB System RAM GPU: NVIDIA GeForce RTX 4060 Laptop GPU (8GB VRAM) # The Secret Sauce (The -cmoe Flag) To make this work properly on any 8GB card, you must use the -cmoe (CPU MoE) flag in llama.cpp. This flag isolates the heavy MoE expert weights directly to system memory (CPU/RAM) while letting your GPU focus strictly on the Attention layers and the KV Cache. It prevents VRAM spillage and holds the throughput rock solid. # The flags: -m "gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf" -cmoe -c 248000 -v Once running, just open the UI on localhost and toggle the new reasoning lightbulb icon in the text input box to watch the model perform multi step thinking. Are you still running smaller models, or are you ready to scale up your budget local setups? Let's discuss in the replies
Original Article
View Cached Full Text

Cached at: 06/08/26, 03:15 AM

Run Gemma 4 26B MoE on 8GB VRAM with 250k context at 20+ tokens/sec

If you own any 8GB VRAM graphics card, stop what you are doing. Local AI just had its absolute “Holy Shit” moment for budget hardware.

Yesterday, I benchmarked Unsloth Gemma 4 12B Q4_K_XL on an 8GB card.

The community went wild but immediately demanded more: “Can we run a 25B+ model on budget GPUs?”

Today, I’m delivering exactly that.

I am running a massive 26B parameter Mixture of Experts (MoE) model locally on a standard 8GB VRAM setup with 250k full native context!.

If you own an RTX 3060, 3070, 4060, or any budget GPU with 8GB of VRAM, the local AI paradigm has completely changed.

The performance metrics are astonishing:

  • 20 tokens/sec flat decode throughput.
  • Stable, flat decode speed even with massive prompts.
  • I threw a 60k token prompt at it, and it still clocked in at 20 TPS without dropping a single frame.

What about prefill?

Yes, Time To First Token (TTFT) is slightly high when swallowing massive contexts. But with a solid 200 tokens/sec prefill speed, the wait is barely noticeable and highly usable.

And this is running completely without Multi Token Prediction (MTP) active.

How is this possible? It’s the magic of Google’s new QAT (Quantization Aware Training) quants for Gemma 4.

The model weight file (unsloth gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf) is only 13.2 GB, making it the ultimate local powerhouse.

The Test Setup:

CPU: Intel Core i7

RAM: 16GB System RAM

GPU: NVIDIA GeForce RTX 4060 Laptop GPU (8GB VRAM)

The Secret Sauce (The -cmoe Flag)

To make this work properly on any 8GB card, you must use the -cmoe (CPU MoE) flag in llama.cpp.

This flag isolates the heavy MoE expert weights directly to system memory (CPU/RAM) while letting your GPU focus strictly on the Attention layers and the KV Cache.

It prevents VRAM spillage and holds the throughput rock solid.

The flags:

-m “gemma-4-26B-A4B-it-qat-UD-Q4_K_XL.gguf” -cmoe -c 248000 -v

Once running, just open the UI on localhost and toggle the new reasoning lightbulb icon in the text input box to watch the model perform multi step thinking.

Are you still running smaller models, or are you ready to scale up your budget local setups? Let’s discuss in the replies

Alok (@analogalok): a new 8GB VRAM GPU dense Local LLM leader was born yesterday

runs on: RTX 4060 / RTX 3070 / RTX 2080. any 8GB card

Qwen 3.5 9B (dense) was the go to for 6-8GB VRAM builds.

Gemma 4 12B QAT (dense) just changed that.

same llama.cpp + cuda 13.2. i7 12700H. 16GB RAM. same -ngl 99

Similar Articles

24+ tok/s from ~30B MoE models on an old GTX 1080 (8 GB VRAM, 128k context)

Reddit r/LocalLLaMA

A developer demonstrates running MoE models like Qwen 3.6 35B-A3B and Gemma 4 26B-A4B at 24+ tok/s on an old GTX 1080 (8GB VRAM) with 128k context using llama.cpp with MoE offloading and TurboQuant KV cache quantization, revealing optimization tricks for Gemma's MTP speculative decoding.