Can I run gpt-oss-120b on an RTX 5080 16GB?

With --n-cpu-moe 29: the MXFP4 GGUF keeps 14.8 GB on the RTX 5080 and 46.4 GB in system RAM, with the experts of 29 of its 36 layers moved there. Whole, gpt-oss-120b needs about 68.6 GB at MXFP4 with 32K tokens of context, 52.6 GB more than the RTX 5080 16GB holds. The smallest setup here that holds gpt-oss-120b at MXFP4 with 32K is A100 80GB.

Why 68.6 GB with vLLM, but 14.8 GB on the RTX 5080 with llama.cpp

The 68.6 GB counts the published checkpoint as vLLM loads it: 60.8 GB of weights, the 32K KV cache, 0.5 GB and 10% overhead. llama.cpp's measured MXFP4 GGUF is 59.0 GB, and its 587 MB of token embeddings stay in RAM. With every layer on the RTX 5080 it takes 60.6 GB at 32K with 1 GB of buffers, 44.6 GB more than it holds, so the experts of 29 layers (45.8 GB) move to system RAM. That leaves 1.22 GB of the 16 GB free, and the PC needs 46.4 GB of free RAM for those experts and the embeddings.

With offload the MXFP4 GGUF with --n-cpu-moe 29 and 32K tokens of context

On the card
14.8 GB
RTX 5080
16 GB, 960 GB/s
In RAM
46.4 GB
Tokens/s
14–24 tokens/s

With the MXFP4 GGUF, --n-cpu-moe 29 and 32K tokens of context it writes about 14–24 tokens/s for one request on an RTX 5080 16GB and dual-channel DDR5-5600.

gpt-oss-120b on the RTX 5080 as the context fills

One request, FP16 KV cache, 0.5 GB plus 10% overhead; the MXFP4 GGUF columns are the measured llama.cpp file with every layer on the GPU and 1 GB of buffers; a minus sign is memory missing, and tight is less than 0.5 GB free.

Context MXFP4FreeTokens/sMXFP4 GGUFFreeTokens/s
4K 67.5 GB −51.5 GB — 59.6 GB −43.6 GB —
8K 67.7 GB −51.7 GB — 59.8 GB −43.8 GB —
16K 68.0 GB −52.0 GB — 60.0 GB −44.0 GB —
32K 68.6 GB −52.6 GB — 60.6 GB −44.6 GB —
64K 69.8 GB −53.8 GB — 61.7 GB −45.7 GB —
128K (full) 72.3 GB −56.3 GB — 64.0 GB −48.0 GB —

--n-cpu-moe for gpt-oss-120b on the RTX 5080

With --n-cpu-moe 29 the MXFP4 GGUF keeps 14.8 GB on the RTX 5080 and 46.4 GB in RAM, about 14–24 tokens/s with DDR5-5600. Measured MXFP4 file, 1 GB of buffers; tokens/s by system RAM speed.

Context--n-cpu-moeOn the cardIn RAM DDR4-3200DDR5-5600DDR5-6400
8K 28 15.5 GB 44.8 GB 9.4–1615–2617–29
32K 29 14.8 GB 46.4 GB 8.8–1514–2416–27
64K 29 15.9 GB 46.4 GB 8.5–1413–2315–25
128K (full) 31 15.0 GB 49.6 GB 7.6–1312–1913–21

gpt-oss-120b on more than one RTX 5080

CardsBest at 32KTokens/sMXFP4 longestMXFP4 tokens/s
2× (32 GB) Nothing fits — Does not fit —
4× (64 GB) Nothing fits — Does not fit —

Tensor parallel with the combined bandwidth, as in vLLM; llama.cpp splits layers by default and runs at about one card's speed.

Other options

Run gpt-oss-120b on the RTX 5080 with llama-server

llama-server -hf ggml-org/gpt-oss-120b-GGUF:MXFP4 -c 32768 --n-cpu-moe 29 -np 1

gpt-oss-120b-MXFP4.gguf, 63.4 GB, from ggml-org/gpt-oss-120b-GGUF (checked 2026-09-29); --n-cpu-moe 29 with -c 32768 is the plan above. -np 1: one slot, one sliding window.

Questions

Can I run gpt-oss-120b on an RTX 5080 16GB?

With --n-cpu-moe 29: the MXFP4 GGUF keeps 14.8 GB on the RTX 5080 and 46.4 GB in system RAM, with the experts of 29 of its 36 layers moved there. Whole, gpt-oss-120b needs about 68.6 GB at MXFP4 with 32K tokens of context, 52.6 GB more than the RTX 5080 16GB holds. The smallest setup here that holds gpt-oss-120b at MXFP4 with 32K is A100 80GB.

How fast is gpt-oss-120b on an RTX 5080 16GB?

With the MXFP4 GGUF, --n-cpu-moe 29 and 32K tokens of context it writes about 14–24 tokens/s for one request on an RTX 5080 16GB and dual-channel DDR5-5600.

Does gpt-oss-120b need --n-cpu-moe on an RTX 5080 16GB?

With --n-cpu-moe 29 the MXFP4 GGUF keeps 14.8 GB on the RTX 5080 and 46.4 GB in RAM, about 14–24 tokens/s with DDR5-5600.

What does a second RTX 5080 16GB change for gpt-oss-120b?

Even two RTX 5080 16GB cards (32 GB) do not hold gpt-oss-120b at 32K.

Try other settings in the VRAM calculator, the speed calculator or the MoE offload planner. See also gpt-oss-120b VRAM requirements, what LLMs an RTX 5080 16GB can run and every pair, or detect your own GPU. Model data checked .