text model · Nemotron 3 · Windows
Can I run Nemotron Cascade 2 30B-A3B on Nvidia GeForce RTX 5090 (32GB)?
Yes. Nemotron Cascade 2 30B-A3B runs on Nvidia GeForce RTX 5090 (32GB) at Q4_K_M (~25.1 GB of ~31 GB usable).
Runs at Q4_K_M using ~25.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 ~5.9 GB of headroom.
- Q4_K_M needed
- ~25.1 GB
- Usable on device
- ~31 GB
- Device memory
- 32 GB
- Best quant
- Q4_K_M
Which quant fits
Run it
Pick your tool. All 3 load the same Q4_K_M weights.
ollama run nemotron-cascade-2:30b llama-cli -hf bartowski/nvidia_Nemotron-Cascade-2-30B-A3B-GGUF:Q4_K_M lms get bartowski/nvidia_Nemotron-Cascade-2-30B-A3B-GGUF - Parameters
- 30B (MoE, 3B active)
- Q4_K_M size
- 23.03 GB
- Q8_0 size
- 31.28 GB
- Context
- 256k
- Ollama tag
- nemotron-cascade-2: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 Nemotron Cascade 2 30B-A3B on other hardware
FAQ
Can Nvidia GeForce RTX 5090 (32GB) run Nemotron Cascade 2 30B-A3B?
Yes. Nemotron Cascade 2 30B-A3B runs on Nvidia GeForce RTX 5090 (32GB) at Q4_K_M (~25.1 GB of ~31 GB usable).
How much memory does Nemotron Cascade 2 30B-A3B need?
Nvidia GeForce RTX 5090 (32GB) has room to spare. At Q4_K_M the weights are ~23.03 GB; with KV cache and runtime overhead, budget ~25.1 GB at a 4k context. It is a Mixture-of-Experts model (30B total / 3B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run Nemotron Cascade 2 30B-A3B 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
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/nemotron-cascade-2-30b-a3b/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.