Gotchi
All posts
BenchmarksJune 13, 202611 min read

Small models, big shift: why efficient local LLMs are winning

The frontier gets the headlines, but 7B–70B open models get the work done. Distillation and quantization changed what 'good enough' means.

Gotchi Team
Engineering

The most important trend in AI isn't at the frontier - it's at the median. Techniques like distillation, better data curation, and 4-bit quantization mean today's mid-size open models outperform the flagship cloud models of eighteen months ago, while running on a laptop.

Capability per gigabyte keeps climbing

  • A quantized 7B model now handles summarization, drafting, and Q&A that needed 70B parameters in 2024.
  • Q4_K_M quantization cuts memory footprints roughly 4× with low single-digit accuracy loss.
  • DeepSeek V3's architecture delivers more quality per parameter - it fits on 32GB machines that can't hold Llama 3.1 70B.
  • Task-tuned small models routinely beat general-purpose giants on the one job they're trained for.

Why this favors local

Cloud vendors have to justify datacenter margins with frontier capability. But most real work - email, documents, code review, research synthesis - sits comfortably within what a local 14B–70B model delivers. When the median task is solved on-device, the cloud premium becomes a subsidy for workloads you don't have.

Local inference on Apple Silicon42 tok/sLlama 3.1 70B, Q4_K_M on M4 Pro

Right-sizing beats maximizing

The practical skill in 2026 isn't picking the biggest model - it's matching model to task. Gotchi auto-detects your hardware, recommends the right quantization, and lets you switch models per conversation or per agent step. Fast small model for triage, larger model for the final draft. That's how local setups quietly outperform a single cloud subscription.


How small models got good: the technical story

Three techniques did most of the work. Distillation transfers capability from a large teacher model to a small student by training the student on the teacher's outputs - which is why a modern 8B model reasons like the 70B models of two generations ago. Data curation replaced 'more tokens' with 'better tokens'; the same parameter count trained on filtered, deduplicated, reasoning-heavy data yields dramatically higher benchmark scores. And post-training - instruction tuning, preference optimization, targeted fine-tunes - closed most of the gap between raw capability and usable assistant behavior.

  • Distillation: small models trained to imitate large ones inherit a surprising fraction of their reasoning.
  • Data quality: curated corpora beat raw web scale - capability per training token keeps rising.
  • Quantization-aware training: newer models are built to survive 4-bit compression with minimal loss.
  • Mixture-of-experts: architectures like DeepSeek's activate only a fraction of weights per token, buying quality per gigabyte of memory.

Reading benchmarks without being fooled

Benchmark tables reward skepticism. MMLU-Pro scores compress at the top; a 2-point gap there rarely translates to a perceptible difference in daily use. Contamination - models trained on benchmark data - inflates some scores. The honest evaluation is your own: take three tasks you actually do (a summarization, a code review, a research question), run them against two or three candidate models, and judge blind. Most users discover their work has a 'good enough' threshold that mid-size models cleared a year ago.

The per-task routing pattern

Once model switching is instant and free, a new pattern emerges that cloud subscriptions can't match: routing by task. A 3B model handles classification and triage at hundreds of tokens per second. A 14B model drafts the routine email. The 70B model gets the final report and the gnarly refactor. In Gotchi, each agent step can specify its own model, so a single workflow uses the small-fast model for filtering and the large-careful model for output - the compute equivalent of not sending a senior engineer to sort the mail.

Triage throughput, 3B model200+ tok/son Apple Silicon - route the easy 80% cheap

What to expect next

The trendline is unambiguous: every release cycle, the capability that required N gigabytes of memory arrives in roughly half of it. On-device NPUs are starting to handle sustained inference workloads that were GPU-only a year ago. The practical implication for anyone planning hardware: buy memory, not hype - unified memory (or VRAM) is the one spec that determines what you can run, and the models that fit it get better for free every quarter.

Find your model

Browse the model library in Gotchi - every major open family, one click to download, tuned to your hardware.

Ready to run AI locally?

Download Gotchi. Open core, local-first, and ready for every model you want to run.