text model · Nemotron · Linux
Can I run Nemotron 3.5 Super VL 120B-A12B on Nvidia DGX Spark (128GB)?
Yes. Nemotron 3.5 Super VL 120B-A12B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~87.4 GB of ~112 GB usable).
Runs at Q4_K_M using ~87.4 GB of ~112 GB usable.
That figure is at a 4k context and moves about ±15% as context length changes. Nvidia DGX Spark (128GB) leaves ~24.6 GB of headroom.
- Q4_K_M needed
- ~87.4 GB
- Usable on device
- ~112 GB
- Device memory
- 128 GB
- Best quant
- Q4_K_M
Which quant fits
Run it
Loads the Q4_K_M weights.
ollama run nemotron-3.5-super:120b-a12b-q4_K_M - Parameters
- 120B (MoE, 12B active)
- Q4_K_M size
- 83.96 GB
- Context
- 1024k
- Ollama tag
- nemotron-3.5-super:120b-a12b-q4_K_M
- Memory
- 128 GB unified
- Usable for weights
- ~112 GB
- Power draw
- ~140 W
- Best runtime
- llama.cpp (CUDA) / Ollama (CUDA)
You could also run
Run Nemotron 3.5 Super VL 120B-A12B on other hardware
FAQ
Can Nvidia DGX Spark (128GB) run Nemotron 3.5 Super VL 120B-A12B?
Yes. Nemotron 3.5 Super VL 120B-A12B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~87.4 GB of ~112 GB usable).
How much memory does Nemotron 3.5 Super VL 120B-A12B need?
Nvidia DGX Spark (128GB) has room to spare. At Q4_K_M the weights are ~83.96 GB; with KV cache and runtime overhead, budget ~87.4 GB at a 4k context. It is a Mixture-of-Experts model (120B total / 12B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run Nemotron 3.5 Super VL 120B-A12B on Linux?
Ollama for a simple setup; vLLM for the most speed. vLLM shines for multi-user serving/throughput. For a single local chat, Ollama or llama.cpp is simpler and lighter.
Embed this
[](https://localmodel.run/can-i-run/nemotron-3.5-super-120b-a12b/nvidia-dgx-spark-128gb) Sources
-
docs.nvidia.com · 2 sources
-
github.com · 1 source
-
nvidia.com · 1 source
-
nvidianews.nvidia.com · 1 source
-
ollama.com · 2 sources
-
registry.ollama.ai · 1 source
-
tomshardware.com · 1 source
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.