Can the NVIDIA RTX A6000 run Olmo 3.1 32B Think?

Yes, it runs well

Runs well. At Q4_K_M it needs about 23.4 GB of 48.0 GB usable, with an estimated speed of 29.3 tok/s.

Best quant: Q4_K_M
Generation speed: 29.3 tok/s
Prompt processing: 865 tok/s
First token (1K prompt): 1.2 s
Largest safe context: 64K

Best app to run it on the NVIDIA RTX A6000

On Windows

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

One command with Ollama’s own build of this model.
Serves an OpenAI-compatible API that other apps and coding tools can use.

ollama run olmo-3.1:32b-think-q4_K_M

LM Studio Point-and-click: search, download and chat in one window.
llama.cpp Usually the first to support new model architectures.

On Linux

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

One command with Ollama’s own build of this model.
Serves an OpenAI-compatible API that other apps and coding tools can use.

ollama run olmo-3.1:32b-think-q4_K_M

vLLM The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
LM Studio Point-and-click: search, download and chat in one window.

Want an agent? Olmo 3.1 32B Think supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Olmo 3.1 32B Think

Recommended for the NVIDIA RTX A6000: Q4_K_M. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run olmo-3.1:32b-think-q4_K_M

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q4_K_M file (opens in a new tab)

huggingface.co/unsloth/Olmo-3.1-32B-Think-GGUF (opens in a new tab)

ollama run hf.co/unsloth/Olmo-3.1-32B-Think-GGUF:Q4_K_M

Original weights · Hugging Face

Full-precision files from Ai2, for fine-tuning, vLLM, Transformers.

huggingface.co/allenai/Olmo-3.1-32B-Think (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Ai2. The weights themselves download from Hugging Face.

github.com/allenai/OLMo (opens in a new tab)

git clone https://github.com/allenai/OLMo

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs well: How well it runs on the NVIDIA RTX A6000: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	32.5 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	12.8 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	11.2 / 15
Match score	81.6 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA RTX A6000

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	16.6 GB	48.0 GB	48.0 tok/s	Runs great	53Fair quality (C) · 53 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	19.5 GB	48.0 GB	37.8 tok/s	Runs great	63Good quality (B) · 63 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	23.4 GB	48.0 GB	29.3 tok/s	Runs well	72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	26.6 GB	48.0 GB	24.2 tok/s	Runs well	73Great quality (A) · 73 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	30.2 GB	48.0 GB	20.3 tok/s	Runs well	75Great quality (A) · 75 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	37.9 GB	48.0 GB	14.9 tok/s	Runs well	76Great quality (A) · 76 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	68.2 GB	48.0 GB	1.6 tok/s	Very slowheavy RAM offload	76Great quality (A) · 76 of 100: how capable the model is at F16, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

73Great quality (A) · 73 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q5_K_M · 56.4 tok/s · Runs great
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 Q4_K_M · 38.4 tok/s · Runs well (tight fit)
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3090 Q4_K_M · 35.6 tok/s · Runs well (tight fit)
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX Q4_K_M · 31.5 tok/s · Runs well (tight fit)
75Great quality (A) · 75 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Q6_K · 47.4 tok/s · Runs great
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (64 GB) Q4_K_M · 17.9 tok/s · Runs well

Quick answers

How much memory does Olmo 3.1 32B Think need on the NVIDIA RTX A6000 48GB?

At Q4_K_M it needs about 23.4 GB. The NVIDIA RTX A6000 48GB has 48.0 GB usable.

How fast is Olmo 3.1 32B Think on the NVIDIA RTX A6000 48GB?

About 29.3 tok/s at Q4_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Olmo 3.1 32B Think should I use on the NVIDIA RTX A6000 48GB?

Q4_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.