@sudoingX: save this one. it answers a question every 24gb GPU owner asks and almost nobody gets right. how much context can i act…
Summary
A user shares detailed VRAM usage measurements for running Qwen 3.6 27b on a 24GB GPU, showing context window sizes and headroom, and notes that a used RTX 3090 performs identically to newer cards.
View Cached Full Text
Cached at: 07/11/26, 01:25 PM
save this one. it answers a question every 24gb GPU owner asks and almost nobody gets right. how much context can i actually run.
here is the whole map for qwen 3.6 27b on a single 24gb card. i measured every rung so you don’t have to guess.
a 4k window costs 16.6gb. barely more than the model itself. you are leaving most of your card unused. 128k is the sweet spot, and it is the number to remember. it costs 18.7gb and leaves you a clean 6gb of headroom, which is exactly what a real agent session needs for tool calls and scratch space. this is where you should live.
262k fits too, at 21.3gb. use it for single giant documents, one shot, no agent. it is tight but it holds. 376k is the wall. 23.6gb, half a gig from the edge. it loads and it runs, but you are living on the fault line, one big prompt from a crash. 384k is where the card says no. out of memory. that is the ceiling of the tier, full stop.
here is the part that makes this a keeper. these numbers are identical on a 3090, a 4090, and a 5090, within 35 megabytes. the vram footprint is a property of the model, not the card. so a 900 dollar used 3090 gives you the exact same context ceiling as the newest flagship. you are not buying more room by spending more money, you already have all of it.
pin this next to your llama.cpp config and stop guessing at your context flag.
so, next question for the room. which tier do i climb next, the 16gb cards where most of you actually live, or the 128gb boxes where the monsters run. drop your vote.
here’s the exact command for the 128k sweet spot, copy paste and go:
llama-server -m qwen3.6-27b-q4_k_m.gguf -ngl 99 -c 131072 -fa on –cache-type-k q4_0 –cache-type-v q4_0 -n 32768
that -n 32768 matters more than people think, it stops long agent writes from truncating mid file. flash attention plus q4 kv is what fits 128k on 24gb at full speed. run it, then tell me your tok/s.
Similar Articles
@sudoingX: anyone running a 16gb card, stop scrolling. @pupposandro and @davideciffa got qwen 35b-a3b down to 13.3gb, measured on …
A technique called luce spark allows Qwen 35B-a3B MoE model to run on a 16GB GPU (like RTX 3090) by learning which experts are frequently used and streaming the rest from RAM, achieving ~100 tok/s without VRAM bottleneck.
Getting close to 100K context on 32GB VRAM with Qwen3.6-27 at Q8
A user shares their attempts and configurations to achieve up to 115K context on a Q8-quantized Qwen3.6-27B model using 32GB VRAM on an RTX 5090, with benchmark results and trade-offs between context length and kv-cache quantization.
Best Settings for 48GB VRAM + Qwen 3.6 27B
A user shares optimized settings for running Qwen3.6 27B (Q8_0) on a dual GPU setup (RTX 4090 + RTX 3090) with llama.cpp, achieving 75-100 t/s and 1500 pp with 250k context.
Qwen 35B-A3B is very usable with 12GB of VRAM
A user benchmarks Qwen 35B-A3B (a 35B MoE model) on a 12GB RTX 3060, finding that 12GB VRAM is a practical sweet spot for running the model with 32k context, achieving ~47 t/s generation.
7900XTX 24GB vram, can finally fit Q6K+MTP with Qwen 3.6 27B at 131k context
A guide on optimizing VRAM usage on an AMD 7900XTX to run a 27B Qwen model with Q6K quantization and 131k context by compiling llama.cpp with OpenBLAS and CUDA_FA_ALL_QUANTS, and using kvcache quantization at q5_0/q4_0.