Background
The post opens with an analogy: traditional large models are like carrying an entire library in your backpack—tens of billions of parameters fully loaded into VRAM. Gemma 4 introduces Per-Layer Embeddings as a smarter solution.
A Library You Can Detach
- Gemma 4's E2B variant has 5.1 billion parameters total.
- Of these, 2.8 billion are static embeddings—tied only to the vocabulary, independent of position.
- Since this part is static, Gemma 4 keeps it on disk and looks it up on demand, leaving only about 2.3 billion parameters resident in VRAM.
- iPhone 17 Pro: ~40 tokens/second via the MLX framework.
- Raspberry Pi 5: community tests show 41.76 tokens/second with an M.2 SSD and sensible quantization.
- Gemma 4 31B placed third at roughly $0.20 per run, behind Opus 4.6 and GPT-5.2.
- ROI exceeded 1100%.
- SauerkrautLM-Doom (1.3M parameters) can beat cloud LLMs on VizDoom control tasks.
- Falcon Perception (0.6B) runs image segmentation on Mac via MLX, outperforming SAM 3.
Analogy from the post: leave the dictionary at the hotel and carry only a portable guide; consult the dictionary when needed.
The Art of Speed
Cost-Effectiveness
On the FoodTruck Bench agentic evaluation:
The takeaway: more parameters ≠ better performance; because of Per-Layer Embeddings, the actual compute burden of the 31B model is far smaller than comparable models.
Lessons for the Industry
The post argues Gemma 4 represents a new design philosophy—efficiency over parameter bloat—supported by examples:
Per-Layer Embeddings open a path for large-embedding + small-operator models: decoupling static from dynamic parts, storage from compute, ownership from usage.
Closing Thought
AI democratization may not mean everyone buys a top-tier GPU—it means ordinary phones, Raspberry Pis, even future smartwatches running capable AI. When large models learn to slim down, they get closer to everyone.
> The highest form of technology is when users no longer feel its presence.
---
*Source commit: 2c47ab1*