text model · Olmo · Windows
Can I run Olmo 3.1 32B Instruct on Nvidia GeForce RTX 4060 Ti (16GB)?
No. Olmo 3.1 32B Instruct needs ~20.3 GB even at Q4_K_M, but Nvidia GeForce RTX 4060 Ti (16GB) only has ~15 GB usable.
Needs ~20.3 GB even at Q4_K_M, but only ~15 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 5.3 GB: Olmo 3.1 32B Instruct needs roughly 20.3 GB at Q4_K_M and Nvidia GeForce RTX 4060 Ti (16GB) leaves only about 15 GB usable for a model. The lightest tracked hardware that runs Olmo 3.1 32B Instruct is the Nvidia GeForce RTX 4090 (24GB) at 24 GB. See Olmo 3.1 32B Instruct on Nvidia GeForce RTX 4090 (24GB).
Too big for Nvidia GeForce RTX 4060 Ti (16GB)'s VRAM, but you could offload some layers to system RAM and still run it at roughly ~5 tok/s, far slower than a model that fits. How this is estimated.
- Q4_K_M needed
- ~20.3 GB
- Usable on device
- ~15 GB
- Device memory
- 16 GB
Which quant fits
- 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
- 16 GB vram
- Usable for weights
- ~15 GB
- Power draw
- ~165 W
- Best runtime
- Ollama (CUDA) / llama.cpp CUDA
What you can run instead
Run Olmo 3.1 32B Instruct on other hardware
FAQ
Can Nvidia GeForce RTX 4060 Ti (16GB) run Olmo 3.1 32B Instruct?
No. Olmo 3.1 32B Instruct needs ~20.3 GB even at Q4_K_M, but Nvidia GeForce RTX 4060 Ti (16GB) only has ~15 GB usable.
How much memory does Olmo 3.1 32B Instruct need?
Nvidia GeForce RTX 4060 Ti (16GB) does not have enough memory. 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-4060-ti-16gb) 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.