Methodology
Every number on RunsOnMy is computed by one small, deterministic JavaScript module that runs the same way at build time, in the Worker and in your browser. Nothing is written by hand per model.
Total memory
total = weights + KV cache + overhead
Weights
When a GGUF build exists on Hugging Face (from the model maker, Unsloth, bartowski, LM Studio Community or ggml-org) we use the real file size of each quant, summing split files. Otherwise we estimate parameters × bits-per-weight ÷ 8 with llama.cpp's average bits per weight:
| Quant | Bits per weight | Quality |
|---|---|---|
| Q2_K | 3 | rough |
| Q3_K_M | 3.91 | usable |
| Q4_K_M | 4.89 | good, most popular |
| Q5_K_M | 5.7 | very good |
| Q6_K | 6.56 | near lossless |
| Q8_0 | 8.5 | effectively lossless |
| F16 | 16 | original weights |
Parameter counts come from the safetensors metadata on Hugging Face. For mixture-of-experts models, all experts must be in memory, so memory uses total parameters. Active parameters (used for speed) are computed from the config: total − MoE layers × (experts − experts per token) × 3 × hidden × expert FFN size.
KV cache
- Standard / GQA / MQA:
2 × layers × KV heads × head dim × context × 2 bytes(FP16). - MLA (DeepSeek, Kimi, GLM-5 families):
layers × (KV latent rank + RoPE dim) × context × 2 bytes, the compressed cache llama.cpp stores. Sparse-attention indexer keys are added when present. - Sliding-window layers (Gemma, gpt-oss and others): those layers are capped at the window size.
- Hybrid linear-attention / state-space layers (Qwen3.5+, Nemotron-H, LFM): only full-attention layers grow with context; the small fixed state is covered by overhead.
- 8-bit or 4-bit KV cache (calculator option) scales the KV term by 0.5 or 0.25.
Pages for models with newer compressed-attention designs we can't model exactly are labeled as upper bounds.
Overhead
0.4 GiB + vocabulary size × 512 × 4 bytes, covering the runtime context and the logits/compute buffer at the default 512-token batch.
Usable memory
- Discrete GPUs: 95% of VRAM (driver and display reserve). Multi-GPU rigs add up their cards.
- Apple Silicon: macOS lets the GPU wire about 75% of unified memory on 64 GB+ Macs and about 67% below that, by default.
- Unified-memory PCs (DGX Spark, Ryzen AI Max): 85% of system memory.
Fits = total ≤ 90% of usable memory. Tight = 90–100%. No = over.
Speed ceiling
Generating one token reads all active weights once, so tokens/sec ≤ memory bandwidth ÷ (weights × active/total parameters). This is an upper bound; real llama.cpp speeds are usually 50–80% of it. We label it an estimate everywhere and will replace it with measured, opt-in benchmark results.
API prices
Prices come from OpenRouter's public models API every 6 hours. Each snapshot is compared to the previous one and every change is logged (change log). Where LiteLLM's MIT-licensed price map has the model maker's own entry, we show it side by side and flag differences.
Automated accuracy checks
Before every build, a check script runs golden tests against hand-computed values and sanity gates on every page. A model page is held back (not published) if its numbers fail, for example missing architecture or memory below the file size. GGUF sizes that disagree with the parameter count are discarded in favour of estimates. The build is blocked if the golden tests fail or more than 20% of pages are held.
Latest run: Nov 17, 2026 · 285 models checked, 0 held · golden tests: 3/3 passed · 145 prices cross-checked with LiteLLM, 30 differ.
Refresh schedule
- Hugging Face models: hourly (new releases get a page within the hour).
- API prices: every 6 hours.
- GPU and Mac specs: from vendor spec pages, re-checked monthly.
Spotted something wrong? Tell us; corrections are logged.