text model · Olmo · Windows
Can I run Olmo 3.1 32B Instruct on Nvidia GeForce RTX 4090 (24GB)?
Yes. Olmo 3.1 32B Instruct runs on Nvidia GeForce RTX 4090 (24GB) at Q4_K_M (~20.3 GB of ~23 GB usable).
Runs at Q4_K_M using ~20.3 GB of ~23 GB usable.
That figure is at a 4k context and moves about ±15% as context length changes. Nvidia GeForce RTX 4090 (24GB) leaves ~2.7 GB of headroom.
- Q4_K_M needed
- ~20.3 GB
- Usable on device
- ~23 GB
- Device memory
- 24 GB
- Best quant
- Q4_K_M
Which quant fits
Running cost · estimate
- Power draw
- ~450 W
- Electricity / 1M tokens
- ~$0.52
At ~$0.15/kWh and the estimated ~36 tok/s, a million generated tokens costs about $0.52 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 olmo-3.1:32b-instruct llama-cli -hf bartowski/allenai_Olmo-3.1-32B-Instruct-GGUF:Q4_K_M lms get bartowski/allenai_Olmo-3.1-32B-Instruct-GGUF - Parameters
- 32B
- Q4_K_M size
- 18.14 GB
- Q8_0 size
- 31.9 GB
- Context
- 64k
- Ollama tag
- olmo-3.1:32b-instruct
- Memory
- 24 GB vram
- Usable for weights
- ~23 GB
- Power draw
- ~450 W
- Best runtime
- vLLM (Linux) / Ollama (CUDA)
You could also run
Run Olmo 3.1 32B Instruct on other hardware
FAQ
Can Nvidia GeForce RTX 4090 (24GB) run Olmo 3.1 32B Instruct?
Yes. Olmo 3.1 32B Instruct runs on Nvidia GeForce RTX 4090 (24GB) at Q4_K_M (~20.3 GB of ~23 GB usable).
How much memory does Olmo 3.1 32B Instruct need?
Nvidia GeForce RTX 4090 (24GB) 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 3.1 32B Instruct 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/olmo-3.1-32b-instruct/nvidia-rtx-4090-24gb) 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.