GPT-OSS 120B needs ~90.2 GB VRAM. NVIDIA DGX Spark 128GB has 108.8 GB. With Q4_K_M quantization, expect ~3 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
Fit status
Tight fit
Decode
2.5 tok/s
TTFT
77567 ms
Safe context
77K
Memory
90.2 GB / 108.8 GB
The model fits in shared memory, but shared-memory bandwidth is now the real limiter.
Fit does not mean dedicated-VRAM speed
Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.
Shared-memory contention still exists
The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.
Prioritize bandwidth, not only capacity
If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | S | Runs well | 2.5 tok/s | 42309 ms | 77K |
| Coding | A | Tight fit | 2.5 tok/s | 77567 ms | 77K |
| Agentic Coding | A | Tight fit | 2.5 tok/s | 112825 ms | 77K |
| Reasoning | A | Tight fit | 2.5 tok/s | 91670 ms | 77K |
| RAG | A | Tight fit | 2.5 tok/s | 141031 ms | 77K |
How GPT-OSS 120B (117B params) fits at each quantization level on NVIDIA DGX Spark 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 45.6 GB | Low | S88 |
Q3_K_S | 3 | 57.3 GB | Low | S88 |
NVFP4 | 4 | 65.5 GB | Medium | S88 |
Q4_K_MBest for your GPU | 4 | 71.4 GB | Medium | S88 |
Q5_K_M | 5 | 84.2 GB | High | F0 |
Q6_K | 6 | 95.9 GB | High | F0 |
Q8_0 | 8 | 125.2 GB | Very High | F0 |
F16 | 16 | 239.8 GB | Maximum | F0 |
Copy-paste commands to run GPT-OSS 120B on your machine.
Run
ollama run gpt-oss:120bYour hardware
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 123B | S | 2.4 tok/s | ||
| 122B | S | 6.6 tok/s | ||
| 119B | S | 7.1 tok/s |
Yes, NVIDIA DGX Spark 128GB can run GPT-OSS 120B with a A grade (Tight fit). Expected decode speed: 2.5 tok/s.
GPT-OSS 120B (117B parameters) requires approximately 90.2 GB of memory with Q4_K_M quantization.
The recommended quantization for GPT-OSS 120B is Q4_K_M, which balances quality and memory efficiency.
On NVIDIA DGX Spark 128GB, GPT-OSS 120B achieves approximately 2.5 tokens per second decode speed with a time-to-first-token of 77567ms using Q4_K_M quantization.
For coding workloads, GPT-OSS 120B on NVIDIA DGX Spark 128GB receives a A grade with 2.5 tok/s and 77K context.
On NVIDIA DGX Spark 128GB, GPT-OSS 120B can safely use up to 77K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.
Prioritize bandwidth, not only capacity. If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Not always. NVIDIA DGX Spark 128GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/gpt-oss-120b-on-dgx-spark-128gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: