Can the UDOO BOLT V8 (8 GB) run Granite 3.3 2B?

Yes, it runs well

Runs well. At Q4_K_M it needs about 3.1 GB of 4.0 GB usable, with an estimated speed of 16.0 tok/s.

Best quant: Q4_K_M
Generation speed: 16.0 tok/s
Prompt processing: 551 tok/s
First token (1K prompt): 1.9 s
Largest safe context: 18K

Best app to run it on the UDOO BOLT V8 (8 GB)

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 ibm-granite/granite-3.3-2b-instruct-GGUF:Q4_K_M

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 ibm-granite/granite-3.3-2b-instruct-GGUF:Q4_K_M

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 3.3 2B

Recommended for the UDOO BOLT V8 (8 GB): 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 granite3.3:2b

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/ibm-granite/granite-3.3-2b-instruct-GGUF (opens in a new tab)

ollama run hf.co/ibm-granite/granite-3.3-2b-instruct-GGUF:Q4_K_M

Original weights · Hugging Face

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

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

No sign-in needed.

Official repo · GitHub

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

github.com/ibm-granite/granite-3.3-language-models (opens in a new tab)

git clone https://github.com/ibm-granite/granite-3.3-language-models

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

How it’s rated

Quality 28Basic quality (D) · 28 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 62/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 UDOO BOLT V8 (8 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.	12.8 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; 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.	9.5 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	62.3 / 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 UDOO BOLT V8 (8 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	2.6 GB	4.0 GB	26.3 tok/s	Runs well	21Basic quality (D) · 21 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	2.8 GB	4.0 GB	20.7 tok/s	Runs well	25Basic quality (D) · 25 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	3.1 GB	4.0 GB	16.0 tok/s	Runs well	28Basic quality (D) · 28 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	3.4 GB	4.0 GB	13.3 tok/s	Runs well	29Basic quality (D) · 29 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	3.7 GB	4.0 GB	11.1 tok/s	Runs welltight fit	29Basic quality (D) · 29 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 60/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	4.3 GB	4.0 GB	6.9 tok/s	Slowover GPU memory limit	30Basic quality (D) · 30 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 44/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	6.7 GB	4.0 GB	—	Won't run	30Basic quality (D) · 30 of 100: how capable the model is at F16, whatever it runs on. Match score 4/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (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

30Basic quality (D) · 30 of 100: how capable the model is at F16, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3060 12GB F16 · 41.0 tok/s · Runs great
30Basic quality (D) · 30 of 100: how capable the model is at F16, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 SUPER F16 · 57.4 tok/s · Runs great
30Basic quality (D) · 30 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4060 Q8_0 · 67.2 tok/s · Runs great
30Basic quality (D) · 30 of 100: how capable the model is at F16, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 9070 XT F16 · 62.7 tok/s · Runs great
30Basic quality (D) · 30 of 100: how capable the model is at F16, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER F16 · 76.5 tok/s · Runs great
30Basic quality (D) · 30 of 100: how capable the model is at F16, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER F16 · 83.8 tok/s · Runs great

Quick answers

How much memory does Granite 3.3 2B need on the UDOO BOLT V8 8GB?

At Q4_K_M it needs about 3.1 GB. The UDOO BOLT V8 8GB has 4.0 GB usable.

How fast is Granite 3.3 2B on the UDOO BOLT V8 8GB?

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

Which quantization of Granite 3.3 2B should I use on the UDOO BOLT V8 8GB?

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.