on

Can the AMD EPYC 7002 / 7003 series NAS (32 GB) run Granite 3.2 2B Instruct?

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

Yes, it runs great

Runs great. At Q5_K_M it needs about 5.2 GB of 26.2 GB usable, with an estimated speed of 45.6 tok/s.

Best quant
Q5_K_M
Generation speed
45.6 tok/s
Prompt processing
158 tok/s
First token (1K prompt)
6.5 s
Largest safe context
128K

Best app to run it on the AMD EPYC 7002 / 7003 series NAS (32 GB)

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 granite3.2:2b

How we choose: the files published for this model, which apps run in a container on a NAS without a graphics card (models run on its processor), and whether the model fits fully in the memory models can use. Details.

Download Granite 3.2 2B Instruct

Recommended for the AMD EPYC 7002 / 7003 series NAS (32 GB): Q5_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 granite3.2:2b

Quantized files · GGUF

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

Download the Q5_K_M file (opens in a new tab)

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

ollama run hf.co/bartowski/ibm-granite_granite-3.2-2b-instruct-GGUF:Q5_K_M

Original weights · Hugging Face

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

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

No sign-in needed.

Links checked 7 hours ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 29Basic quality (D) · 29 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q5_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 great
How well it runs on the AMD EPYC 7002 / 7003 series NAS (32 GB): 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.13.1 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); fewer when it goes past that limit.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.4.5 / 15
Match score57.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 AMD EPYC 7002 / 7003 series NAS (32 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 4.4 GB 26.2 GB 90.7 tok/s Runs great 21Basic quality (D) · 21 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 4.6 GB 26.2 GB 71.4 tok/s Runs great 25Basic quality (D) · 25 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 4.9 GB 26.2 GB 55.2 tok/s Runs great 28Basic quality (D) · 28 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 5.2 GB 26.2 GB 45.6 tok/s Runs great 29Basic quality (D) · 29 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 5.4 GB 26.2 GB 38.3 tok/s Runs great 29Basic quality (D) · 29 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 6.1 GB 26.2 GB 28.1 tok/s Runs well 30Basic quality (D) · 30 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.4 GB 26.2 GB 13.0 tok/s Runs well 30Basic quality (D) · 30 of 100: how capable the model is at F16, whatever it runs on. Match score 54/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

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?