gpt-oss 120B on NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)

Can the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB) run gpt-oss 120B?

Yes, it runs great

Runs great. At MXFP4 it needs about 75.7 GB of 102 GB usable, with an estimated speed of 61.3 tok/s.

Best quant: MXFP4
Generation speed: 61.3 tok/s
Prompt processing: 4,066 tok/s
First token (1K prompt): 0.3 s
Largest safe context: 128K

Best app to run it on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)

On Linux

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

One command with Ollama’s own build of this model.
Serves an OpenAI-compatible API that other apps and coding tools can use.

ollama run gpt-oss:120b

LM Studio Point-and-click: search, download and chat in one window.
llama.cpp Usually the first to support new model architectures.

Reverse engineering? Serve gpt-oss 120B locally and use it from Ghidra, IDA Pro, Binary Ninja, radare2 or JADX with one of these:

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download gpt-oss 120B

Recommended for the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB): MXFP4. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run gpt-oss:120b

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the MXFP4 file (opens in a new tab)

huggingface.co/ggml-org/gpt-oss-120b-GGUF (opens in a new tab)

ollama run hf.co/ggml-org/gpt-oss-120b-GGUF:MXFP4

Original weights · Hugging Face

Full-precision files from OpenAI, for fine-tuning, vLLM, Transformers.

huggingface.co/openai/gpt-oss-120b (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from OpenAI. The weights themselves download from Hugging Face.

github.com/openai/gpt-oss (opens in a new tab)

git clone https://github.com/openai/gpt-oss

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at MXFP4, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great: How well it runs on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	37.8 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	92.8 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`MXFP4`	75.7 GB	102 GB	61.3 tok/s	Runs great	84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab) Original weights (opens in a new tab)
`F16`	243 GB	102 GB	—	Won't run	84Great quality (A) · 84 of 100: how capable the model is at F16, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. AMD Ryzen AI Max+ 395 (128 GB) MXFP4 · 47.7 tok/s · Runs great
84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (128 GB) MXFP4 · 86.0 tok/s · Runs great
84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GB10 (128 GB) MXFP4 · 56.9 tok/s · Runs great
84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 92/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell MXFP4 · 181 tok/s · Runs great
84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. Apple M2 Ultra (192 GB) MXFP4 · 111 tok/s · Runs great
84Great quality (A) · 84 of 100: how capable the model is at MXFP4, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (256 GB) MXFP4 · 113 tok/s · Runs great

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.