FitLLM

Can I run Hy3 on an RTX 5080 (16GB)?

❌ No — Hy3 (Q4_K_M) needs 205 GB but the RTX 5080 has 16 GB

Computed with the open FitLLM engine — accurate per-layer KV-cache modeling, not a naive estimate. Updated 2026-07-10.

Memory breakdown (Q4_K_M, F16 KV, 33K context)

Model weights170 GB
KV cache10.0 GB
Runtime overhead + reserve24.9 GB
Total used205 / 16 GB
Short by189 GB

Max context that fits at Q4_K_M: does not fit.

Every quantization on the RTX 5080

Weight quantWeightsFits (KV F16)Used @32K
Q4_K_M170 GB❌ won't fit205 / 16.0 GB
Q5_K_M198 GB❌ won't fit237 / 16.0 GB
Q6_K228 GB❌ won't fit270 / 16.0 GB
Q8_0296 GB❌ won't fit346 / 16.0 GB
FP16557 GB❌ won't fit638 / 16.0 GB

Lower weight quants free memory at some output-quality cost — Q4 is the common sweet spot; below that quality drops faster.

KV cache is F16 here (llama.cpp default). Drop it to Q8/Q4 (-ctk/-ctv) for more context.

▶ Open the interactive calculator (this exact setup)

Embed this verdict

Live badge for your README or model card — recomputed by the engine, never stale:

[![fits: Hy3 on RTX 5080](https://img.shields.io/endpoint?url=https%3A%2F%2Ffitllm.run%2Fapi%2Fbadge%3Fmodel%3DHy3%26gpu%3DRTX%25205080)](https://fitllm.run/can-i-run/hy3-on-rtx-5080)

fit badge preview ← renders like this, live.

Or from your terminal (exit 0/1 — works as a pre-download guard):

npx fitllm "Hy3" --gpu "RTX 5080"

Why most VRAM calculators get this wrong

Hy3 is a Mixture-of-Experts: ~21B of 298.8B parameters are active per token, but all 298.8B must sit in memory. Naive calculators that size memory off active params (or KV off all layers) get this wrong.

What fits on the RTX 5080 instead

same GPU Models that fit on the RTX 5080: Gemma 4 e2b, Gemma 4 e4b, Gemma 4 12b, Llama-3.2-3B-Instruct, Llama-3.1-8B-Instruct, Qwen3-0.6B, Qwen3-1.7B, Llama-3.2-1B-Instruct, Gemma-3-1B-it.

same model GPUs that run Hy3: —.

Reproduce it

Hy3 = 298.8B (21B active, MoE), 80 layers. The RTX 5080 has 16GB / 960GB/s. Same math, open source: fitllm-engine. GGUF bpw from llama.cpp.

All numbers are computed by the open-source fitllm-engine (MIT) from official model config.json values — reproduce or audit them yourself. Estimates; real usage varies with runtime (llama.cpp / MLX / Ollama), driver and display. Found a mismatch? Report it. · FitLLM home