What if Qwen3.8 27B runs out of memory on RTX 4090 24GB?

Unload idle models, cap GPU layers with --num-gpu, and cut context to 2048. KV cache grows with context and is the usual OOM cause.

Should I use Q4 or Q8 for Qwen3.8 27B?

Start Q4_K_M. Bigger model at Q4 beats smaller at Q8. Use Q8 only with 2GB+ headroom.

can i run · seo

Yes — Qwen3.8 27B runs on RTX 4090 24GB

Qwen3.8 27B (27.8B dense) needs 20GB VRAM at Q5 vs your 24GB VRAM. Estimated ~31–42 tok/s.

Best all-rounder you can actually run. Vision + reasoning + 256k context, Apache-2.0, Unsloth Q4 around 17 GB.

best fit on this rig · weights + KV + headroom

Q5 · 20GB weights+1GB KV @ 8kfits GPU~31–42 tok/s

quant	weights	+ KV 8k	fits 24GB?
Q4	17GB	~18GB	✓ yes
Q5	20GB	~21GB	✓ yes
Q8	30GB	~31GB	× tight/no
FP16	56GB	~57GB	× tight/no

File size ≠ runtime. KV grows with context — halve to 4k/2k if long chats OOM. Leave 1–2GB free.

ollama run qwen3.8:27b

Run it: 1) install Ollama · 2) copy command · 3) verify with ollama ps (want 100% GPU).

huggingface GGUF

faq · straight answers

Can Qwen3.8 27B run on RTX 4090 24GB?

Qwen3.8 27B (27.8B dense) needs 20GB VRAM at Q5 vs your 24GB VRAM. Estimated ~31–42 tok/s. Model context 256k. Compare with all models or re-check with your exact specs on the bench.

What if it OOMs?

Unload with ollama stop, cap layers --num-gpu 28, cut context to 2k. See the OOM fixer on the homepage.

Q4 or Q8 on this rig?

Start Q5. Bigger model at Q4 beats smaller at Q8. Only go Q8 if 2GB+ headroom remains.

How fast will it be?

About ~31–42 tok/s when 100% on GPU. Any CPU offload drops speed 5–20× — check ollama ps.

Is Apache-2.0 commercial-safe?

Yes — Apache-2.0 allows commercial use.

also fits RTX 4090 24GB

MiniCPM5 2B · FP16 Mistral Small 3.2 · Q5 Nemotron 3 Nano 30B-A3B · Q4

Qwen3.8 27B on other rigs

8 GB laptop RTX 3060 12GB RTX 4070 12GB 2x RTX 3090 (48GB)RTX 5090 32GB Mac M4 16GB

Check your own rig in 15 seconds →

real-time global visitors

Coarse location inferred from browser timezone without fingerprinting or tracking cookies. Every blinking node represents an active hardware builder browsing the open-weight registry.

growingearly builders · be earlylive0 active

recent pings · timezone-derived0 nodes

listening for hardware builders…

┌────────────────────────────────────────────────────────────────┐ │· -180° · · · · -90° · · · · · · 0° · · · · · · +90° · · +180° ·│ │ __..---..__ .---. _..----.._ _.._ │ │ .' · NA · '. / · \ .' · EU · '. .'·AP │ │ / *US/CA* · \| GL |· / *UK/DE/FR* \ / *JP/CN│ │| [W-COAST] · || · · · | · | [CENTRAL] · | | *IN/KR│ │ \ [E-COAST]· / \ · / · \ [MEDIT] · / \ *SG/AU│ │ '. · · · .' '---' '. · · · .' '. · │ │ '-·_____·-' · · '-·____·-' '--· │ │ · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · │ │ _.._ _.._ · · · _.._ │ │ .' · '. .' · '. .' · '. │ │ / LATAM \ / AFRICA \ / ANZ \ │ │ | *BR/MX/AR|· | *ZA/KE/NG| | *AU/NZ* | │ │ \ · · / \ · · / | · · | │ │ '. · .' '. · .' \ · · / │ │ '..' '..' '.____.' │ │[LAT -60°] · · · · · · · · · · · · · · · · · · · · · ·[LAT +60°]│ │ >> ACTIVE NODE RADAR · TELEMETRY MESH // SYNCED VIA TIMEZONE << │ └────────────────────────────────────────────────────────────────┘