on

Can the Raspberry Pi 5 (2 GB) run TMax 4B?

42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking.

No, it doesn’t fit

No. TMax 4B needs about 2.6 GB even at Q2_K; the Raspberry Pi 5 (2 GB) has 1.2 GB usable.

Download TMax 4B

Original weights · Hugging Face

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

huggingface.co/allenai/tmax-4b (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_K, 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 Won't run
How well it runs on the Raspberry Pi 5 (2 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.5.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.0.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.0.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.0.0 / 15
Match score5.8 / 100

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

It doesn’t fit, so only a reduced share of the quality points counts and fit, speed and memory use score zero.

Every quantization on the Raspberry Pi 5 (2 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 2.6 GB 1.2 GB — Won't run 42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 5/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 3.0 GB 1.2 GB — Won't run 51Fair quality (C) · 51 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q4_K_M 3.5 GB 1.2 GB — Won't run 57Good quality (B) · 57 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 4.0 GB 1.2 GB — Won't run 59Good quality (B) · 59 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 4.4 GB 1.2 GB — Won't run 60Good quality (B) · 60 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 5.4 GB 1.2 GB — Won't run 61Good quality (B) · 61 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 9.4 GB 1.2 GB — Won't run 61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 8/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.

Hardware that can run it

Models that do run on the Raspberry Pi 5 (2 GB)

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?