text model · Mistral · Linux
Can I run Devstral 2 123B on Nvidia DGX Spark (128GB)?
Yes. Devstral 2 123B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~73.3 GB of ~112 GB usable).
Runs at Q4_K_M using ~73.3 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 ~38.7 GB of headroom.
- Q4_K_M needed
- ~73.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
- ~$1.9
At ~$0.15/kWh and the estimated ~3 tok/s, a million generated tokens costs about $1.9 in electricity. TDP is the peak draw, so this is an upper bound. Assumptions.
Run it
Pick your tool. All 3 load the same Q4_K_M weights.
ollama run devstral-2:123b llama-cli -hf unsloth/Devstral-2-123B-Instruct-2512-GGUF:Q4_K_M lms get unsloth/Devstral-2-123B-Instruct-2512-GGUF - Parameters
- 123B
- Q4_K_M size
- 69.75 GB
- Q8_0 size
- 123.73 GB
- Context
- 256k
- Ollama tag
- devstral-2:123b
- 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 Devstral 2 123B on other hardware
FAQ
Can Nvidia DGX Spark (128GB) run Devstral 2 123B?
Yes. Devstral 2 123B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~73.3 GB of ~112 GB usable).
How much memory does Devstral 2 123B need?
Nvidia DGX Spark (128GB) has room to spare. At Q4_K_M the weights are ~69.75 GB; with KV cache and runtime overhead, budget ~73.3 GB at a 4k context.
What is the best tool to run Devstral 2 123B 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/devstral-2-123b/nvidia-dgx-spark-128gb) Sources
-
docs.nvidia.com · 2 sources
-
github.com · 1 source
-
huggingface.co · 2 sources
-
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.