Skip to content
RfRigFit

No. Qwen3.6 27B does not fit on the GeForce RTX 3060 12GB at Q4. The estimate is 17.4 GB and usable memory is 11.4 GB.

Can the GeForce RTX 3060 12GB run Qwen3.6 27B?

Data updated . Last reviewed the same day, when this catalog snapshot was written.

Usable memory on this 12 GB VRAM config is 11.4 GB (95% of the sticker figure). A result under 2 GB of headroom is labeled tight.

Quant ladder

Estimated memory for Qwen3.6 27B on GeForce RTX 3060 12GB
QuantEstimateHeadroomEst. tok/sVerdict
Q417.4 GB-6.0 GB21.4 tok/sNo
Q829.1 GB-17.7 GB12.6 tok/sNo
FP1666.7 GB-55.3 GB6.48 tok/sNo

KV cache at 8K and 32K

FP16 KV-cache estimate: 0.5 GB at 8,192 tokens and 2.1 GB at 32,768 tokens. GQA counts two tensors (K and V) for the stored KV heads and head dimension. 48 linear-attention layers are omitted because they keep a fixed state, which this catalog does not size.

Offload

About 5.4 GB of the Q4 weights sit outside usable VRAM. A partial offload would need at least that much free system RAM. This catalog does not record system RAM, so offload is not counted as a fit.

Ollama

This command pulls the Q4_K_M file from unsloth/Qwen3.6-27B-GGUF, the Hub repo whose file size is used above. It is not an official Ollama library tag.

ollama run hf.co/unsloth/Qwen3.6-27B-GGUF:Q4_K_M

What fits instead

All hardware for Qwen3.6 27B · All models for the GeForce RTX 3060 12GB

Questions

How much memory does Qwen3.6 27B need at Q4?
The Q4 figure used here is 17.4 GB. GGUF file size plus an FP16 KV-cache estimate at 8,192 tokens. The cache counts only the layers and heads named in the method on the About page.
Can the GeForce RTX 3060 12GB run Qwen3.6 27B?
No. Qwen3.6 27B does not fit on the GeForce RTX 3060 12GB at Q4. The estimate is 17.4 GB and usable memory is 11.4 GB.
What is the cheapest catalog device that runs Qwen3.6 27B at Q4?
Radeon RX 7900 XT, list price $899.
How fast is Qwen3.6 27B on the GeForce RTX 3060 12GB, as a bandwidth estimate?
About 21.4 tok/s at Q4. That is device bandwidth divided by active weight bytes, not a measured run.