Can I run Qwen3.6 35B-A3B on the GeForce RTX 4090?
Runs greatQ4_K_M fits in VRAM with 1.6 GB to spare: Runs great, est. 171.9 tok/s (137.5–206.2, calibrated estimate ±20%).
24 GB VRAM · 1,008.0 GB/s · FP16 82.6 TFLOPS. Assumes 32 GB of DDR5-5600 system RAM, Windows with this GPU driving the display, 8k context and an f16 KV cache. The verdict and quant file above stay the same anywhere from 16 to 128 GB of system RAM. The GeForce RTX 3090 Ti has the same memory setup (24 GB, 1,008.0 GB/s), so its generation-speed estimate is the same; only prompt processing differs. Prompt processing: about 9,387 tok/s (5,632–13,141, rough estimate ±40%) here vs about 4,546 tok/s (2,727–6,364, rough estimate ±40%) on the GeForce RTX 3090 Ti.
Every quant of Qwen3.6 35B-A3B on the GeForce RTX 4090
| Quant | File size | Verdict | Speed | Memory | Runs as | Notes |
|---|---|---|---|---|---|---|
| Q2_K | 13.51 GB | Runs great | est. 197.5 tok/s158.0–236.9calibrated estimate ±20% | 13.8 / 24.0 GB | Full GPU | — |
| IQ4_XS | 19.70 GB | Runs great | est. 183.2 tok/s146.6–219.9calibrated estimate ±20% | 19.9 / 24.0 GB | Full GPU | — |
| Q4_K_Mbaseline | 22.29 GB | Runs great | est. 171.9 tok/s137.5–206.2calibrated estimate ±20% | 22.4 / 24.0 GB | Full GPU | — |
| Q8_0 | 37.81 GB | Runs well | est. 57.8 tok/s40.4–75.1theoretical estimate ±30% | 22.3 / 24.0 GB + 16.8 GB RAM | MoE experts in RAM | Not fully on the GPU — Runs great needs the whole model in GPU memory |
Models with a thinking mode spend extra tokens thinking, so their speed thresholds are 1.5× stricter (30 / 12 / 3 tok/s). With thinking turned off, a model may do one grade better.
Where the memory goes at Q4_K_M
- Weights
- 21.1 GB
- KV cache
- 0.2 GB
- Compute buffer
- 0.6 GB
- OS reserve
- 0.6 GB
- Free
- 1.6 GB
1.20 GB of the 22.29 GB file stays off the graphics card: llama.cpp keeps the input embedding table in system RAM and does not load the 0.90 GB MTP (multi-token prediction) block by default. Turning on MTP speculative decoding (llama.cpp --spec-type draft-mtp) needs memory for that block plus KV cache for it.
Context length vs. KV cache
| Context | KV f16 | KV q8_0 | KV q4_0 |
|---|---|---|---|
| 4k | 21.7 GBRuns great est. 175.4 tok/s140.4–210.5calibrated estimate ±20% | 21.7 GBRuns great est. 177.2 tok/s141.7–212.6calibrated estimate ±20% | 21.7 GBRuns great est. 178.1 tok/s142.5–213.7calibrated estimate ±20% |
| 8k | 21.8 GBRuns great est. 171.9 tok/s137.5–206.2calibrated estimate ±20% | 21.8 GBRuns great est. 175.2 tok/s140.1–210.2calibrated estimate ±20% | 21.7 GBRuns great est. 177.0 tok/s141.6–212.4calibrated estimate ±20% |
| 16k | 22.1 GBRuns great est. 165.1 tok/s132.1–198.1calibrated estimate ±20% | 21.9 GBRuns great est. 171.4 tok/s137.1–205.6calibrated estimate ±20% | 21.8 GBRuns great est. 174.9 tok/s139.9–209.9calibrated estimate ±20% |
| 32k | 22.6 GBRuns great est. 153.1 tok/s122.5–183.7calibrated estimate ±20% | 22.2 GBRuns great est. 164.2 tok/s131.4–197.0calibrated estimate ±20% | 22.1 GBRuns great est. 170.9 tok/s136.7–205.1calibrated estimate ±20% |
| 64k | 23.5 GBRuns well est. 123.2 tok/s86.2–160.1theoretical estimate ±30% | 22.9 GBRuns great est. 151.5 tok/s121.2–181.9calibrated estimate ±20% | 22.6 GBRuns great est. 163.3 tok/s130.7–196.0calibrated estimate ±20% |
| 128k | 25.5 GBRuns well est. 88.5 tok/s62.0–115.1theoretical estimate ±30% | 24.2 GBRuns well est. 116.7 tok/s81.7–151.7theoretical estimate ±30% | 23.6 GBRuns well est. 136.9 tok/s95.9–178.0theoretical estimate ±30% |
| 256k | 29.4 GBRuns well est. 56.7 tok/s39.7–73.7theoretical estimate ±30% | 26.9 GBRuns well est. 79.9 tok/s55.9–103.9theoretical estimate ±30% | 25.5 GBRuns well est. 103.5 tok/s72.5–134.6theoretical estimate ±30% |
S = Runs great · A = Runs well · B = Runs slowly · F = Won't run
At Q4_K_M the verdict stays Runs great up to 32k context with an f16 KV cache, and up to 64k with q8_0.
Estimated speed
- Generation
- est. 171.9 tok/s (137.5–206.2, calibrated estimate ±20%)
- Prompt processing
- about 9,387 tok/s (5,632–13,141, rough estimate ±40%)
Measured on this exact combination
No public measurement for this exact combination yet; the numbers above are estimates.
If this is not enough
A larger model that also runs well on the GeForce RTX 4090
Runs wellK2-Horizon MoVA 36B-A4B: Runs well, est. 82.6 tok/s (57.8–107.4, theoretical estimate ±30%)
How to run it
Commands for the Q4_K_M file. Both tools download from Hugging Face on first run.
File: Qwen_Qwen3.6-35B-A3B-Q4_K_M.gguf (22.29 GB) from bartowski/Qwen_Qwen3.6-35B-A3B-GGUF.
llama-server -hf bartowski/Qwen_Qwen3.6-35B-A3B-GGUF:Q4_K_M -c 8192 -ngl all -fa on- -ngl all loads every layer on the GPU.
- -fa on enables flash attention (needed for KV cache quantization).
- --cache-type-k q8_0 --cache-type-v q8_0 shrinks the KV cache to 0.09 GB at 8k context.
PowerShell (quit the Ollama tray app first):
$env:OLLAMA_CONTEXT_LENGTH="8192"; ollama serve
ollama run hf.co/bartowski/Qwen_Qwen3.6-35B-A3B-GGUF:Q4_K_M- Ollama defaults to 4k context on GPUs under 24 GB. Set OLLAMA_CONTEXT_LENGTH when starting the server, or /set parameter num_ctx inside the chat.
/set parameter num_ctx 8192
Related pages
Guide: How much VRAM do local LLMs need? GPU requirements for 8–32 GB (2026)
Other models on the GeForce RTX 4090
Qwen3.6 35B-A3B on other hardware
Frequently asked questions
Can I run Qwen3.6 35B-A3B on the GeForce RTX 4090?
Q4_K_M fits in VRAM with 1.6 GB to spare: Runs great, est. 171.9 tok/s (137.5–206.2, calibrated estimate ±20%). Q4_K_M needs 21.8 GB at 8k context; this setup has 23.4 GB of usable memory and 28.0 GB of free system RAM.
How much context can Qwen3.6 35B-A3B use on the GeForce RTX 4090?
At Q4_K_M the verdict stays Runs great up to 32k context with an f16 KV cache (0.7 GB of KV) and up to 64k with a q8_0 KV cache (0.7 GB). The model supports up to 256k.
Which quant should I use, and how fast is it?
Q4_K_M (22.29 GB) is the recommended balance: Runs great, est. 171.9 tok/s (137.5–206.2, calibrated estimate ±20%). It is also the largest tracked file that gets this verdict.
Speeds are estimates from memory bandwidth, calibrated against public benchmarks, and each one comes with an error band and a confidence label. Real results vary with drivers, backend, context length and thermals.