text model · Granite · Windows
Can I run Granite 4.1 30B on Nvidia GeForce RTX 5090 (32GB)?
Yes. Granite 4.1 30B runs on Nvidia GeForce RTX 5090 (32GB) at Q4_K_M (~19.1 GB of ~31 GB usable).
Runs at Q4_K_M using ~19.1 GB of ~31 GB usable.
That figure is at a 4k context and moves about ±15% as context length changes. Nvidia GeForce RTX 5090 (32GB) leaves ~11.9 GB of headroom.
- Q4_K_M needed
- ~19.1 GB
- Usable on device
- ~31 GB
- Device memory
- 32 GB
- Best quant
- Q4_K_M
Which quant fits
Running cost · estimate
- Power draw
- ~575 W
- Electricity / 1M tokens
- ~$0.35
- Pays for itself after
- ~13,327M tok
At ~$0.15/kWh and the estimated ~69 tok/s, a million generated tokens costs about $0.35 in electricity. Versus a hosted API at ~$0.5 per million tokens, the ~$1,999 Nvidia GeForce RTX 5090 (32GB) pays for itself after roughly 13,327 million tokens, so local hardware is mostly a fixed cost, not a per-token one. 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
- 32 GB vram
- Usable for weights
- ~31 GB
- Power draw
- ~575 W
- Best runtime
- vLLM (Linux) / Ollama (CUDA)
You could also run
Run Granite 4.1 30B on other hardware
FAQ
Can Nvidia GeForce RTX 5090 (32GB) run Granite 4.1 30B?
Yes. Granite 4.1 30B runs on Nvidia GeForce RTX 5090 (32GB) at Q4_K_M (~19.1 GB of ~31 GB usable).
How much memory does Granite 4.1 30B need?
Nvidia GeForce RTX 5090 (32GB) 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 Windows?
LM Studio for a simple setup; Ollama (CUDA) for the most speed. AMD GPUs run via Vulkan/ROCm at roughly half CUDA throughput. NVIDIA is the smooth path on Windows.
Embed this
[](https://localmodel.run/can-i-run/granite-4.1-30b/nvidia-rtx-5090-32gb) Sources
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.