Can OLMo 2 32B run on NVIDIA V100 32GB?

YES — Tight Fit

A83Great

Estimated from fit model

OLMo 2 32B needs ~27.8 GB VRAM. NVIDIA V100 32GB has 32.0 GB. With Q4_K_M quantization, expect ~33 tok/s.

Runtime: OllamaCapacity: TightBandwidth: HighStack: BasicBottleneck: Balanced

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 27.8 GB, 33.4 tok/s, Tight fit

27.8 GB required32.0 GB available

87% VRAM used

Fit status

Tight fit

Decode

33.4 tok/s

TTFT

5803 ms

Safe context

Memory

27.8 GB / 32.0 GB

Memory breakdown

Weights19.5 GB

KV Cache3.9 GB

Runtime1.2 GB

Headroom3.2 GB

See how fast it feels

See how fast it feelsOLMo 2 32B on NVIDIA V100 32GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API.

When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed.

Key benefits of running locally:
  - Full privacy: your prompts never leave your machine
  - No per-token cost or rate limits
  - Works offline once the model is downloaded
  - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb:

  Model size     Q4 (4-bit)    Q8 (8-bit)    FP16
  7B params      ~4.3 GB       ~7.5 GB       ~14 GB
  13B params     ~7.9 GB       ~13.9 GB      ~26 GB
  70B params     ~42.7 GB      ~74.9 GB      ~140 GB

Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 33.4 tok/s decode · 5.8s TTFT (warm) · 83 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

No major red flags

This recommendation has enough memory headroom and acceptable estimated speed for the selected workload.

Best improvement path

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	S	Runs well	33.4 tok/s	3165 ms	4K
Coding	A	Tight fit	33.4 tok/s	5803 ms	4K
Agentic Coding	A	Runs with offload	33.4 tok/s	8441 ms	4K
Reasoning	A	Tight fit	33.4 tok/s	6858 ms	4K
RAG	A	Runs with offload	33.4 tok/s	10551 ms	4K

Inference speed

OLMo 2 32B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for OLMo 2 32B at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~66 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / Mac	Memory	Quant	Speed (tok/s)	Fits?
RTX 5090 32GB	32 GB	Q4_K_M	66.4	Tight
MacBook Pro M4 Max 128GB	128 GB	Q4_K_M	33.2	Fits
MacBook Pro M4 Max 64GB	64 GB	Q4_K_M	33.2	Fits
Mac Studio M3 Ultra 256GB	256 GB	Q4_K_M	30.8	Fits
Mac Studio M2 Ultra 128GB	128 GB	Q4_K_M	25.7	Fits
RTX 4090 24GB	24 GB	Q4_K_M	24.8	Heavy offload
Mac Studio M1 Ultra 128GB	128 GB	Q4_K_M	24.3	Fits
RX 7900 XTX 24GB	24 GB	Q4_K_M	22.9	Heavy offload
RTX 3090 24GB	24 GB	Q4_K_M	21.2	Heavy offload
MacBook Pro M4 Pro 48GB	48 GB	Q4_K_M	20.9	Tight
MacBook Pro M3 Max 64GB	64 GB	Q4_K_M	13.3	Fits
MacBook Pro M1 Max 64GB	64 GB	Q4_K_M	12.2	Fits
RTX 4080 Super 16GB	16 GB	Q4_K_M	9.0	Too big
RTX 4070 12GB	12 GB	Q4_K_M	3.1	Too big
RTX 3060 12GB	12 GB	Q4_K_M	2.0	Too big
RTX 4060 8GB	8 GB	Q4_K_M	2.0	Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How OLMo 2 32B (32B params) fits at each quantization level on NVIDIA V100 32GB (32.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	12.5 GB	Low	A80
Q3_K_S	3	15.7 GB	Low	A82
NVFP4	4	17.9 GB	Medium	A82
Q4_K_M	4	19.5 GB	Medium	A81
Q5_K_MBest for your GPU	5	23.0 GB	High	A81
Q6_K	6	26.2 GB	High	F0
Q8_0	8	34.2 GB	Very High	F0
F16	16	65.6 GB	Maximum	F0

Get started

Copy-paste commands to run OLMo 2 32B on your machine.

Run

lms load OLMo-2-0325-32B-Instruct && lms server start

Your hardware

More models your NVIDIA V100 32GB can run

Model	Params	Grade	Decode
Qwen 3.6 35B A3B	35B	S	76.6 tok/s
Qwen 3.5 35B A3B	35B	S	83.3 tok/s
Kimi Linear 48B A3B	48B	A	15.4 tok/s

Frequently asked questions

Can NVIDIA V100 32GB run OLMo 2 32B?

Yes, NVIDIA V100 32GB can run OLMo 2 32B with a A grade (Tight fit). Expected decode speed: 33.4 tok/s.

How much VRAM does OLMo 2 32B need?

OLMo 2 32B (32B parameters) requires approximately 27.8 GB of memory with Q4_K_M quantization.

What is the best quantization for OLMo 2 32B?

The recommended quantization for OLMo 2 32B is Q4_K_M, which balances quality and memory efficiency.

What speed will OLMo 2 32B run at on NVIDIA V100 32GB?

On NVIDIA V100 32GB, OLMo 2 32B achieves approximately 33.4 tokens per second decode speed with a time-to-first-token of 5803ms using Q4_K_M quantization.

Can NVIDIA V100 32GB run OLMo 2 32B for coding?

For coding workloads, OLMo 2 32B on NVIDIA V100 32GB receives a A grade with 33.4 tok/s and 4K context.

What context window can OLMo 2 32B use on NVIDIA V100 32GB?

On NVIDIA V100 32GB, OLMo 2 32B can safely use up to 4K tokens of context. The model's official context limit is 4K, but available memory constrains the safe maximum.

See all results for NVIDIA V100 32GB See all hardware for OLMo 2 32B

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/olmo-2-32b-on-v100-32gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: