text model · OLMo · Linux
Can I run OLMo 2 32B Instruct on Nvidia DGX Spark (128GB)?
Yes. OLMo 2 32B Instruct runs on Nvidia DGX Spark (128GB) at Q4_K_M (~20.3 GB of ~112 GB usable).
Runs at Q4_K_M using ~20.3 GB of ~112 GB usable. You have room for FP16 for higher quality.
That figure is at a 4k context and moves about ±15% as context length changes. Nvidia DGX Spark (128GB) leaves ~91.7 GB of headroom, room to step up to FP16 for higher quality.
- Q4_K_M needed
- ~20.3 GB
- Usable on device
- ~112 GB
- Device memory
- 128 GB
- Best quant
- Q4_K_M
Which quant fits
Running cost · estimate
- Power draw
- ~140 W
- Electricity / 1M tokens
- ~$0.58
At ~$0.15/kWh and the estimated ~10 tok/s, a million generated tokens costs about $0.58 in electricity. TDP is the peak draw, so this is an upper bound. Assumptions.
Run it
Pick your tool. All 2 load the same Q4_K_M weights.
llama-cli -hf unsloth/OLMo-2-0325-32B-Instruct-GGUF:Q4_K_M lms get unsloth/OLMo-2-0325-32B-Instruct-GGUF How to run it
On Linux use Ollama (One-line install, simple single-user UX.).
- Parameters
- 32B
- Q4_K_M size
- 18.14 GB
- Q8_0 size
- 31.9 GB
- Context
- 4k
- 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 OLMo 2 32B Instruct on other hardware
FAQ
Can Nvidia DGX Spark (128GB) run OLMo 2 32B Instruct?
Yes. OLMo 2 32B Instruct runs on Nvidia DGX Spark (128GB) at Q4_K_M (~20.3 GB of ~112 GB usable).
How much memory does OLMo 2 32B Instruct need?
Nvidia DGX Spark (128GB) has room to spare. At Q4_K_M the weights are ~18.14 GB; with KV cache and runtime overhead, budget ~20.3 GB at a 4k context.
What is the best tool to run OLMo 2 32B Instruct 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/olmo-2-32b/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
-
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.