RUNLOCALAIv38
->Will it run?Best GPUCompareTroubleshootStartLearnPulseModelsHardwareToolsBench
Run check
RUNLOCALAI

Independently operated catalog for local-AI hardware and software. Hand-written verdicts. Source-cited claims. Reproducible commands when we have them.

OP·Eruo Fredoline
DIR
  • Models
  • Hardware
  • Tools
  • Benchmarks
TOOLS
  • Will it run?
  • Compare hardware
  • Cost vs cloud
  • Choose my GPU
  • Prompting kits
  • Quick answers
REF
  • All buyer guides
  • Learn local AI
  • Methodology
  • Glossary
  • Errors KB
  • Trust
EDITOR
  • About
  • Author
  • How we make money
  • Editorial policy
  • Contact
LEGAL
  • Privacy
  • Terms
  • Sitemap
MAIL · MONTHLY DIGEST
Get monthly local AI changes
Monthly recap. No spam.
DISCLOSURE

Some links on this site are affiliate links (Amazon Associates and other first-class retailers). When you buy through them, we earn a small commission at no extra cost to you. Affiliate links do not influence our verdicts — there are cards we rate highly that we don't have affiliate relationships with, and cards that sell well that we refuse to recommend. Read more →

© 2026 runlocalai.coIndependently operated
RUNLOCALAI · v38
Glossary / Neural network architectures / MoE Routing
Neural network architectures

MoE Routing

MoE routing is the gating mechanism that decides which experts a token activates in a Mixture-of-Experts layer. Top-k routing (each token picks its k highest-scoring experts) is dominant — Mixtral and DeepSeek use top-2 and top-8 respectively.

Routing quality depends on training: untrained or poorly-trained routers cluster tokens onto a few experts (load imbalance), wasting capacity. Auxiliary load-balancing losses during training fix this.

At inference, routing introduces an all-to-all communication step in distributed setups; on a single GPU, it's a sparse gather. Quantizing experts independently is harder than quantizing dense weights — different experts have different activation distributions.

Practical example

An operator quantizing Mixtral 8x7B to run on a single 24 GB GPU discovers that naively applying a uniform Q4_K_M scheme across all experts leaves some experts noticeably more degraded than others, because MoE routing during training didn't distribute tokens evenly — a handful of experts saw far more training signal than others and have different activation ranges. Tools like llama.cpp's importance-matrix quantization help by calibrating per-tensor scales against a real text sample rather than assuming uniform distributions, meaningfully closing the gap versus naive quantization. At serving time, the operator also notices that batching requests with very different topics hurts throughput more than expected on a single GPU, since divergent routing decisions per token mean less benefit from batched matmuls than a dense model would give — the sparse gather pattern doesn't batch as cleanly as dense compute does.

Related terms

Mixture of Experts (MoE)Expert ParallelismDense Model

Reviewed by Eruo Fredoline. See our editorial policy.

Buyer guides
  • Best GPU for local AI →
  • Best laptop for local AI →
  • Best Mac for local AI →
When it doesn't work
  • CUDA out of memory →
  • Ollama running slowly →
  • ROCm not detected →