on

Can the AMD Radeon PRO W7800 32GB run Granite Vision 3.2 2B?

26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At F16 it needs about 8.8 GB of 32.0 GB usable, with an estimated speed of 47.9 tok/s.

Best quant
F16
Generation speed
47.9 tok/s
Prompt processing
18,808 tok/s
First token (1K prompt)
0.3 s
Largest safe context
128K

Best app to run it on the AMD Radeon PRO W7800 32GB

On Windows

Lemonade

Desktop app · runs on llama.cpp, ONNX Runtime GenAI (Ryzen AI NPU)

  • AMD’s own app: llama.cpp tuned for Radeon on Vulkan and ROCm.
lemonade pull bartowski/ibm-granite_granite-vision-3.2-2b-GGUF:F16
  • LM Studio Point-and-click: search, download and chat in one window.
  • Ollama One command with Ollama’s own build of this model.

On Linux

Lemonade

Desktop app · runs on llama.cpp, ONNX Runtime GenAI (Ryzen AI NPU)

  • AMD’s own app: llama.cpp tuned for Radeon on Vulkan and ROCm.
lemonade pull bartowski/ibm-granite_granite-vision-3.2-2b-GGUF:F16
  • LM Studio Point-and-click: search, download and chat in one window.
  • Ollama One command with Ollama’s own build of this model.

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 Granite Vision 3.2 2B

Recommended for the AMD Radeon PRO W7800 32GB: F16. 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 granite3.2-vision:2b-fp16

Quantized files · GGUF

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

huggingface.co/bartowski/ibm-granite_granite-vision-3.2-2b-GGUF (opens in a new tab)

ollama run hf.co/bartowski/ibm-granite_granite-vision-3.2-2b-GGUF

Original weights · Hugging Face

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

huggingface.co/ibm-granite/granite-vision-3.2-2b (opens in a new tab)

No sign-in needed.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, 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 great
How well it runs on the AMD Radeon PRO W7800 32GB: 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.11.7 / 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.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.6.4 / 15
Match score58.1 / 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 AMD Radeon PRO W7800 32GB

Quant Memory needed Available Speed Runs Quality Download
Q2_K 4.1 GB 32.0 GB 336 tok/s Runs great 18Basic quality (D) · 18 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 4.3 GB 32.0 GB 264 tok/s Runs great 21Basic quality (D) · 21 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 52/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 4.7 GB 32.0 GB 204 tok/s Runs great 24Basic quality (D) · 24 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 5.0 GB 32.0 GB 169 tok/s Runs great 25Basic quality (D) · 25 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 5.3 GB 32.0 GB 142 tok/s Runs great 25Basic quality (D) · 25 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 6.0 GB 32.0 GB 104 tok/s Runs great 26Basic quality (D) · 26 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 8.8 GB 32.0 GB 47.9 tok/s Runs great 26Basic quality (D) · 26 of 100: how capable the model is at F16, whatever it runs on. Match score 58/100 (quality, fit, speed and memory use) sets the ranking. 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

Quick answers

How much memory does Granite Vision 3.2 2B need on the PRO W7800 32GB?

At F16 it needs about 8.8 GB. The PRO W7800 32GB has 32.0 GB usable.

How fast is Granite Vision 3.2 2B on the PRO W7800 32GB?

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

Which quantization of Granite Vision 3.2 2B should I use on the PRO W7800 32GB?

F16. 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.

Was this page helpful?