Skip to content
RfRigFit

No. gpt-oss-20b does not fit on the GeForce RTX 3060 12GB at Q4. The estimate is 11.8 GB and usable memory is 11.4 GB.

Can the GeForce RTX 3060 12GB run gpt-oss-20b?

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 gpt-oss-20b on GeForce RTX 3060 12GB
QuantEstimateHeadroomEst. tok/sVerdict
Q411.8 GB-0.4 GB180 tok/sNo
Q812.3 GB-0.9 GB173 tok/sNo
FP1650.2 GB-38.8 GB50.0 tok/sNo

KV cache at 8K and 32K

FP16 KV-cache estimate: 0.2 GB at 8,192 tokens and 0.8 GB at 32,768 tokens. GQA counts two tensors (K and V) for the stored KV heads and head dimension. config.json also sets a sliding window of 128 tokens. The figures above assume every counted layer stores the full context, so they can overstate cache on sliding layers.

Offload

About 0.2 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/gpt-oss-20b-GGUF, the Hub repo whose file size is used above. It is not an official Ollama library tag.

ollama run hf.co/unsloth/gpt-oss-20b-GGUF:Q4_K_M

What fits instead

All hardware for gpt-oss-20b · All models for the GeForce RTX 3060 12GB

Questions

How much memory does gpt-oss-20b need at Q4?
The Q4 figure used here is 11.8 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 gpt-oss-20b?
No. gpt-oss-20b does not fit on the GeForce RTX 3060 12GB at Q4. The estimate is 11.8 GB and usable memory is 11.4 GB.
What is the cheapest catalog device that runs gpt-oss-20b at Q4?
Radeon RX 7600 XT, list price $329.
How fast is gpt-oss-20b on the GeForce RTX 3060 12GB, as a bandwidth estimate?
About 180 tok/s at Q4. That is device bandwidth divided by active weight bytes, not a measured run.