No — not on this device

gpt-oss 120B at MXFP4 needs 61.4 GB against 51.2 GB usable, and the shortfall of 10.2 GB is more than 32 GB of system RAM can cover at a tolerable speed. A smaller sibling or a lower quantisation is the honest answer here.

Does not fit 8K context MXFP4 · 60.5 GB Apache 2.0 Released Aug 2025 Native MXFP4

Designed to land on one 80 GB card. Only ~5B parameters are active per token.

What hardware do I need for gpt-oss 120B? →

Fits instead: gpt-oss 20B (11.6 GB)

The VRAM budget

weights 60.5 GB
Weights 60.5 GB KV cache @ 8K 0.29 GB Runtime overhead 0.6 GB Over budget 10.2 GB past 51.2 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
MXFP4 60.5 GB 61.4 GB ~6.3 Reference 10.2 GB over

Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. This model interleaves sliding-window layers (128 tokens, 1 global in 2), which is why its cache barely grows with context.

How to run it

terminal
$ llama-server \
    -hf openai/gpt-oss-120b:MXFP4 \
    -c 8192 -ngl 29

The engine underneath most of the others. Every knob is exposed. More on llama.cpp.

01Download is 60.5 GB. Keep it on an SSD — a first load off a spinning disk takes minutes.
02With no GPU, thread count matters more than clock. Start at one thread per physical core.
03If it falls back to CPU silently, drop the context first, then step down a quantisation.
See all models for this rig Compare with another model