on

Can the Arduino UNO Q (4 GB) run GLiDE 0.8B?

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

Yes, but slowly

Slow. At Q3_K_M it needs about 1.3 GB of 2.8 GB usable, with an estimated speed of 5.1 tok/s.

Best quant
Q3_K_M
Generation speed
5.1 tok/s
Prompt processing
10.2 tok/s
First token (1K prompt)
100.0 s
Largest safe context
127K

Best app to run it on the Arduino UNO Q (4 GB)

On Linux on ARM boards

Docker Model Runner

Command line + local API · runs on llama.cpp, vLLM

  • Handy if you already work in Docker.
docker model run hf.co/fastino/GLiDE-0.8B

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 GLiDE 0.8B

Original weights · Hugging Face

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

huggingface.co/fastino/GLiDE-0.8B (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 9Basic quality (D) · 9 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 45/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q3_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 Slow
How well it runs on the Arduino UNO Q (4 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.4.2 / 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.5.3 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.10.6 / 15
Match score45.2 / 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 Arduino UNO Q (4 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 1.2 GB 2.8 GB 6.5 tok/s Slow 7Basic quality (D) · 7 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 44/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 1.3 GB 2.8 GB 5.1 tok/s Slow 9Basic quality (D) · 9 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 45/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q4_K_M 1.4 GB 2.8 GB 3.9 tok/s Slow 10Basic quality (D) · 10 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 45/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 1.5 GB 2.8 GB 3.2 tok/s Slow 10Basic quality (D) · 10 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 46/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 1.5 GB 2.8 GB 2.7 tok/s Very slow 10Basic quality (D) · 10 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 46/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 1.7 GB 2.8 GB 2.0 tok/s Very slow 11Basic quality (D) · 11 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 47/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 2.4 GB 2.8 GB 0.9 tok/s Very slowtight fit 11Basic quality (D) · 11 of 100: how capable the model is at F16, whatever it runs on. Match score 46/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 GLiDE 0.8B need on the Arduino UNO Q 4GB?

At Q3_K_M it needs about 1.3 GB. The Arduino UNO Q 4GB has 2.8 GB usable.

How fast is GLiDE 0.8B on the Arduino UNO Q 4GB?

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

Which quantization of GLiDE 0.8B should I use on the Arduino UNO Q 4GB?

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

Was this page helpful?