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 / Dense Model
Neural network architectures

Dense Model

A dense model activates every parameter on every forward pass — the default architecture for transformers like Llama, Qwen, and Mistral 7B. Distinct from sparse / Mixture-of-Experts models, which route each token through a subset of expert sub-networks.

Dense models are simpler to serve (no routing overhead, simpler quantization paths, no all-to-all communication) but pay full compute cost at inference. A 70B dense model does ~70B parameters × 2 FLOPs × tokens of work per forward pass.

For local AI, dense remains the dominant deployment shape because tooling support is universal and a single dense model fits a single GPU more cleanly than an MoE of equivalent quality.

Practical example

An operator choosing between Mistral 7B (dense) and Mixtral 8x7B (MoE, ~13B active parameters) for a single-GPU deployment has to weigh VRAM against compute differently for each. The dense 7B model at Q4_K_M needs roughly 4-5 GB and runs every one of its parameters on every token — predictable, simple to reason about, and it quantizes cleanly with any GGUF tool. Mixtral needs VRAM for all 8 experts (quality per active-parameter is better) but only computes through 2 of them per token, so it's cheaper per-token than a dense 47B-parameter model would be despite similar total size. For a memory-constrained single-GPU box where total VRAM is the binding constraint rather than compute, the dense model is often the simpler, more predictable choice — no routing surprises, no per-expert quantization tuning.

Related terms

Mixture of Experts (MoE)Transformer

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 →