Fetching from the wire…
Top 5 · 2026-06-07 · source-backed
Google DeepMind shipped Quantization-Aware Training checkpoints for every Gemma 4 size, and the headline number is genuinely useful: the smallest model goes from 11.4GB to 1.1GB. That's 0.84GB if you go text-only. Up to ~72% lower VRAM and 2x faster inference on mobile NPUs, with quality preserved because QAT bakes the quantization into training rather than bolting it on after. Source: Google / MarkTechPost
The reason this lands today, next to a story about AI data center buildout hitting 0.8% of US GDP, is that local inference is the pressure valve. Not everything needs to hit a frontier API. A 1.1GB model that runs on a phone NPU or a cheap edge box is the difference between an agent that costs per-token and one that costs nothing after you've downloaded it.
The release came with same-day support across the stack. Q4_0 GGUF for llama.cpp, a new mobile-specialized quant format, compressed tensors for vLLM, plus Ollama and vLLM running it out of the gate. That same-day part matters more than people give it credit for. A model you can't deploy until the tooling catches up is a press release. A model that runs in Ollama the day it drops is a tool.
Now the gotcha, because there's always one. Unsloth's Daniel Han flagged that naive QAT-to-Q4_0 conversion actually loses accuracy. The dynamic GGUF recovers it. So if you grab these and do the obvious conversion, you can end up worse off than you expected and blame the model. Use the dynamic GGUF builds. This is exactly the kind of detail that costs you an afternoon of confused benchmarking if you don't know it going in.
What to do: if you've got any workload running a small model locally, classification, routing, cheap summarization, the grunt work an Adaptive RAG router hands off, re-benchmark it against quantized Gemma 4. The VRAM math alone might let you consolidate two GPUs down to one, or move a task from cloud to a box under your desk. And keep the dynamic-GGUF note pinned somewhere, because you will forget it and you will waste the afternoon.
Each link below shares sources, entities, or timing with this story.
Google DeepMind released Gemma 4 on April 2 with four model sizes (E2B, E4B, 26B MoE, 31B Dense) under Apache 2.0. Multimodal (text, vision, audio). 256K context. Native thinking and tool-calling optimized for agentic workflows. Day-zero ecosystem support across vLLM, llama.cp...
Google released open-source Multi-Token Prediction (MTP) drafters for the Gemma 4 model family. The concept: pair a heavy target model (Gemma 4 31B) with a lightweight drafter that predicts several future tokens in parallel. The target model verifies the predictions in a singl...
Gemma 4 12B dropped June 3, and the spec sheet is the kind of thing I read twice to make sure I wasn't misreading it. 11.95 billion params, Apache 2.0, reads text, image, audio, and video. No separate vision encoder. No separate audio encoder. The model handles all of it nativ...
Alibaba released Qwen3.6-27B on April 22. Dense architecture. Open weights. 77.2% on SWE-bench Verified, within 3.7 points of Claude Opus 4.6. On SkillsBench, it scores 48.2% versus its own 397B MoE predecessor's 30.0%. That's a 77% improvement with 14.8x fewer parameters. Let...
Unsloth's changelog shows GGUF quantizations compressing GLM-5.2's 1.51TB BF16 weights to 217GB at 1-bit, bringing the strongest text-only open model into reach of a single high-memory local rig. The same update adds Gemma 4 MTP with auto speculative decoding for roughly 2x fa...
Amid a week of pricing and commerce stories, here's hard tech you can actually download. Google released DiffusionGemma on June 10, a 26B-parameter Mixture-of-Experts model (3.8B active) that generates text by diffusion instead of left-to-right decoding. The architecture is th...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.