Can OLMo 2 32B run on Radeon Pro W6800 32GB?

YES — Tight Fit

A81Great
Estimated from fit model

OLMo 2 32B needs ~27.5 GB VRAM. Radeon Pro W6800 32GB has 32.0 GB. With Q4_K_M quantization, expect ~16 tok/s.

Runtime: llama.cppCapacity: TightBandwidth: MediumStack: StandardBottleneck: Balanced
Share:

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.5 GB, 15.9 tok/s, Tight fit
27.5 GB required32.0 GB available
86% VRAM used

Fit status

Tight fit

Decode

15.9 tok/s

TTFT

12204 ms

Safe context

4K

Memory

27.5 GB / 32.0 GB

Memory breakdown

Weights19.5 GB
KV Cache3.9 GB
Runtime0.9 GB
Headroom3.2 GB

See how fast it feels

See how fast it feelsOLMo 2 32B on Radeon Pro W6800 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: 15.9 tok/s decode · 12.2s TTFT (warm) · 40 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

WorkloadGradeFitDecodeTTFTContext
ChatARuns well15.9 tok/s6657 ms4K
CodingATight fit15.9 tok/s12204 ms4K
Agentic CodingARuns with offload15.9 tok/s17751 ms4K
ReasoningATight fit15.9 tok/s14423 ms4K
RAGARuns with offload15.9 tok/s22189 ms4K

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 / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M66.4Tight
MacBook Pro M4 Max 128GB
128 GBQ4_K_M33.2Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M33.2Fits
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M30.8Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M25.7Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M24.8Heavy offload
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M24.3Fits
RX 7900 XTX 24GB
24 GBQ4_K_M22.9Heavy offload
NVIDIARTX 3090 24GB
24 GBQ4_K_M21.2Heavy offload
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M20.9Tight
MacBook Pro M3 Max 64GB
64 GBQ4_K_M13.3Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M12.2Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M9.0Too big
NVIDIARTX 4070 12GB
12 GBQ4_K_M3.1Too big
NVIDIARTX 3060 12GB
12 GBQ4_K_M2.0Too big
NVIDIARTX 4060 8GB
8 GBQ4_K_M2.0Too 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 Radeon Pro W6800 32GB (32.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
12.5 GB
LowA80
Q3_K_S
3
15.7 GB
LowA82
NVFP4
4
17.9 GB
MediumA82
Q4_K_M
4
19.5 GB
MediumA81
Q5_K_MBest for your GPU
5
23.0 GB
HighA81
Q6_K
6
26.2 GB
HighF0
Q8_0
8
34.2 GB
Very HighF0
F16
16
65.6 GB
MaximumF0

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 Radeon Pro W6800 32GB can run

ModelParamsGradeDecodeCapabilities
AlibabaQwen 3.6 35B A3B35BS36.4 tok/s
AlibabaQwen 3.5 35B A3B35BS39.6 tok/s
Moonshot AIKimi Linear 48B A3B48BB6.3 tok/s

Frequently asked questions

Can Radeon Pro W6800 32GB run OLMo 2 32B?

Yes, Radeon Pro W6800 32GB can run OLMo 2 32B with a A grade (Tight fit). Expected decode speed: 15.9 tok/s.

How much VRAM does OLMo 2 32B need?

OLMo 2 32B (32B parameters) requires approximately 27.5 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 Radeon Pro W6800 32GB?

On Radeon Pro W6800 32GB, OLMo 2 32B achieves approximately 15.9 tokens per second decode speed with a time-to-first-token of 12204ms using Q4_K_M quantization.

Can Radeon Pro W6800 32GB run OLMo 2 32B for coding?

For coding workloads, OLMo 2 32B on Radeon Pro W6800 32GB receives a A grade with 15.9 tok/s and 4K context.

What context window can OLMo 2 32B use on Radeon Pro W6800 32GB?

On Radeon Pro W6800 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 Radeon Pro W6800 32GBSee 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-radeon-pro-w6800-32gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: