Can I run this LLM? Real file sizes, live from Hugging Face.
All models › Qwen3.8-9B-Distill

Qwen3.8-9B-Distill requirements — can you run it?

~9.2B parameters · 5 quantizations measured · updated 2026-08-16 · source: empero-ai/Qwen3.8-9B-Distill-GGUF

Run Qwen3.8-9B-Distill (Q4_K_M) — copy-paste:
# llama.cpp (auto-downloads the GGUF)
llama-cli -hf empero-ai/Qwen3.8-9B-Distill-GGUF:Q4_K_M

# Ollama (pulls straight from Hugging Face)
ollama run hf.co/empero-ai/Qwen3.8-9B-Distill-GGUF:Q4_K_M

# LM Studio: search "empero-ai/Qwen3.8-9B-Distill-GGUF" in the model browser

Commands load the exact quant measured on this page.

Every quantization: real file size vs what you actually need

QuantFile (measured)VRAM/RAM needed (8K ctx)Runs on (first fit)
Q4_K_M5.8 GB8.4 GBRTX 3060 12GB
Q5_K_M6.6 GB9.5 GBRTX 3060 12GB
Q6_K7.6 GB10.6 GBRTX 3060 12GB
Q8_09.8 GB13.2 GBRTX 4060 Ti 16GB
BF1618.4 GB23.6 GBRTX 5090 32GB

KV cache uses a flat +20% context/overhead rule because this repo does not publish its config; exact numbers may differ for long contexts. MoE models keep all experts in memory — total size counts, not just active params. Longer context grows the KV cache — use the selector above.

Can I run Qwen3.8-9B-Distill on my GPU? (Q4_K_M recommended quant)

HardwareMemoryVerdictEst. speed
RTX 3060 12GB12 GBRUNS~47 tok/s
RTX 4060 Ti 16GB16 GBRUNS~37 tok/s
RTX 3090 24GB24 GBRUNS~121 tok/s
RTX 4090 24GB24 GBRUNS~131 tok/s
RTX 5090 32GB32 GBRUNS~233 tok/s
RTX PRO 6000 96GB96 GBRUNS~233 tok/s
Mac 16GB unified16 GBRUNS~13 tok/s
Mac 32GB unified32 GBRUNS~19 tok/s
Mac 64GB unified64 GBRUNS~35 tok/s
Mac 128GB unified128 GBRUNS~52 tok/s
Mac 256GB unified256 GBRUNS~71 tok/s
Mac 512GB unified512 GBRUNS~106 tok/s
32GB system RAM (CPU)32 GBRUNS~6 tok/s
64GB system RAM (CPU)64 GBRUNS~6 tok/s
128GB system RAM (CPU)128 GBRUNS~10 tok/s
256GB system RAM (CPU)256 GBRUNS~10 tok/s
1TB server RAM (CPU)1024 GBRUNS~26 tok/s
2TB server RAM (CPU)2048 GBRUNS~26 tok/s

Speed = decode tok/s estimated from memory bandwidth ÷ measured file size (× MoE active share). Real numbers vary ±30% by runtime and settings.

How much VRAM does Qwen3.8-9B-Distill need?

The honest answer: 8.4 GB at the Q4_K_M quant with 8K context — that is the measured file size (5.8 GB) plus KV cache and runtime overhead. The smallest published build needs 8.4 GB; the lossless one needs 23.6 GB.
Cheapest hardware that runs it: Used RTX 3060 12GB (~$250, used market) — see which GPU to buy.

Can I run it with CPU offload?

Yes, if combined RAM+VRAM ≥ file size — but generation speed is limited by memory bandwidth. Expect roughly: DDR5 dual channel ~10-30 tok/s for small MoE actives, single digits for big ones, 0.1-1 tok/s when experts page from disk. CPU-only is fine for batch jobs, painful for chat.

Why do other sites show different numbers?

Most pages compute weights from a formula (params × bits/8). We use the actual file sizes published in GGUF repos, which include the embedding table, unquantized tensors, and container overhead — that is why our numbers can differ from a naive calculation.

FAQ

How much VRAM does Qwen3.8-9B-Distill need?

The measured answer: 8.4 GB at the Q4_K_M quant with 8K context. The smallest published build needs 8.4 GB; the lossless (F16/BF16) build needs 23.6 GB. These are real GGUF file sizes from Hugging Face, not formula estimates.

Can I run Qwen3.8-9B-Distill on a 24GB GPU (RTX 3090/4090)?

Yes — at Q4_K_M (8.4 GB). Quants that fit 24GB: Q4_K_M, Q5_K_M, Q6_K, Q8_0, BF16.

How fast will Qwen3.8-9B-Distill run?

Decode speed is memory-bandwidth-bound. At Q4_K_M: roughly 131 tok/s on an RTX 4090, 121 tok/s on an RTX 3090, 52 tok/s on an M-series Mac with 128GB, and 6.5 tok/s on CPU with dual-channel DDR4 — estimates from measured file size, MoE active-parameter share and memory bandwidth.

Can I run Qwen3.8-9B-Distill on CPU with system RAM?

Yes, if your usable RAM is at least the file size. At Q4_K_M you need ~8.4 GB of RAM. CPU generation is memory-bandwidth-bound: expect single-digit tok/s for large MoE models, 10-30 tok/s for small active params, and below 1 tok/s when experts page from disk.

Why do VRAM numbers for Qwen3.8-9B-Distill differ between sites?

Most sites compute weights from a formula (params x bits/8). ModelFit uses the actual GGUF file sizes published on Hugging Face, which include the embedding table, unquantized tensors, and container overhead — so our numbers reflect what you really download and load.

More models

Qwen3.8-27Bmeasured requirementsQwen3.8-27B-Uncensoredmeasured requirementsQwen3.8-27B-Uncensored-HauhauCS-Aggressive-MTPmeasured requirementsQwen3.8-27B-TURBO-Fable-Cold-Fusion-735-882-Heretic-Uncensored-NEO-CODER-MAX-MTPmeasured requirementsQwen3.8-27B-GSQ-RCOmeasured requirementsQwen3.8-27Bmeasured requirementsQwen3.8-27B-OBLITERATEDmeasured requirementsQwen3.8-4B-Distillmeasured requirements
Share this page: 𝕏 Post Reddit Hacker News Telegram WhatsApp More…