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
  1. >
  2. Home
  3. /Learn
  4. /Courses
  5. /Understanding AI Models
  6. /Ch. 2
Understanding AI Models

02. Parameter Count Guide

Chapter 2 of 20 · 10 min
KEY INSIGHT

Parameter count predicts hardware requirements better than it predicts capability.

Parameter count is the most discussed model spec, so understanding what it means-and what it does not mean-is essential.

Where parameters come from:

A transformer language model has several parameter groups:

  • Embedding layer: vocab_size x embedding_dim. For a 32k vocabulary with 4096-dim embeddings, this alone is ~131M parameters.
  • Attention weights: 4 x layers x head_count x head_dim�. The Q, K, V, and output projections for each layer.
  • FFN (feed-forward) weights: typically 4 x embedding_dim x ff_dim. This is usually 60-70% of total parameters in dense models.
  • Layer norms: a few thousand parameters per layer, negligible in total count.

Why parameter count varies in meaning:

A 7B model with different architectures has different capability profiles despite the same parameter count. MoE models (covered in Chapter 3) can match dense models with far fewer active parameters per token.

Rough capability guide (as of early 2026):

Parameters Approximate capability Notes
1-3B Simple tasks, fast inference Good for classification, extraction
7B General purpose, decent reasoning Minimum for coherent long-form output
13B Noticeably better reasoning Often runs on consumer GPUs
33B+ Strong reasoning, long context Requires 24GB+ VRAM
70B+ Near-top reasoning Often MoE, 4096 context minimum

The catch: Two 7B models from different families or training runs can differ more in capability than a 7B and a 13B from the same lineage. Parameter count is a rough guide, not a capability guarantee.

Local verification checkpoint

Run the smallest example from this chapter in a local workspace and record the package version, runtime, data path, and observed output. If the result depends on model size, vector count, CPU/GPU backend, or available memory, note that constraint beside the exercise so the lesson remains reproducible.

EXERCISE

Find the parameter counts and architectural differences between Llama 3.1 8B and Mistral 7B. Calculate what percentage of parameters come from attention vs FFN layers for each.

← Chapter 1
What the Numbers Mean
Chapter 3 →
Dense vs Mixture of Experts