Skip to content
RfRigFit

No. gpt-oss-120b does not fit on the GeForce RTX 5090 at Q4. The estimate is 63.1 GB and usable memory is 30.4 GB.

Can the GeForce RTX 5090 run gpt-oss-120b?

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

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

Quant ladder

Estimated memory for gpt-oss-120b on GeForce RTX 5090
QuantEstimateHeadroomEst. tok/sVerdict
Q463.1 GB-32.7 GB654 tok/sNo
Q863.7 GB-33.3 GB648 tok/sNo
FP16280 GB-250.0 GB176 tok/sNo

KV cache at 8K and 32K

FP16 KV-cache estimate: 0.3 GB at 8,192 tokens and 1.2 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 32.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/gpt-oss-120b-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-120b-GGUF:Q4_K_M

What fits instead

All hardware for gpt-oss-120b · All models for the GeForce RTX 5090

Questions

How much memory does gpt-oss-120b need at Q4?
The Q4 figure used here is 63.1 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 5090 run gpt-oss-120b?
No. gpt-oss-120b does not fit on the GeForce RTX 5090 at Q4. The estimate is 63.1 GB and usable memory is 30.4 GB.
What is the cheapest catalog device that runs gpt-oss-120b at Q4?
Framework Desktop 128GB, list price $3,449.
How fast is gpt-oss-120b on the GeForce RTX 5090, as a bandwidth estimate?
About 654 tok/s at Q4. That is device bandwidth divided by active weight bytes, not a measured run.