text model · Granite · Linux
Can I run Granite 4.1 30B on Nvidia DGX Spark (128GB)?
Yes. Granite 4.1 30B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~19.1 GB of ~112 GB usable).
Runs at Q4_K_M using ~19.1 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 ~92.9 GB of headroom, room to step up to FP16 for higher quality.
- Q4_K_M needed
- ~19.1 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
Loads the Q4_K_M weights.
ollama run granite4.1:30b - Parameters
- 28.9B
- Q4_K_M size
- 17 GB
- Q8_0 size
- 31 GB
- Context
- 128k
- Ollama tag
- granite4.1:30b
- 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 Granite 4.1 30B on other hardware
FAQ
Can Nvidia DGX Spark (128GB) run Granite 4.1 30B?
Yes. Granite 4.1 30B runs on Nvidia DGX Spark (128GB) at Q4_K_M (~19.1 GB of ~112 GB usable).
How much memory does Granite 4.1 30B need?
Nvidia DGX Spark (128GB) has room to spare. At Q4_K_M the weights are ~17 GB; with KV cache and runtime overhead, budget ~19.1 GB at a 4k context.
What is the best tool to run Granite 4.1 30B 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
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/granite-4.1-30b/nvidia-dgx-spark-128gb) Sources
-
docs.nvidia.com · 2 sources
-
github.com · 1 source
-
huggingface.co · 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.