dots.llm1 Instruct on Arduino UNO Q (2 GB)

Can the Arduino UNO Q (2 GB) run dots.llm1 Instruct?

No, it doesn’t fit

No. dots.llm1 Instruct needs about 66.1 GB even at Q2_K; the Arduino UNO Q (2 GB) has 1.2 GB usable.

Download dots.llm1 Instruct

Recommended: Q2_K. Every other quantization has its own download link in the table below.

Quantized files · GGUF

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

Download the Q2_K files (opens in a new tab)

huggingface.co/unsloth/dots.llm1.inst-GGUF (opens in a new tab)

ollama run hf.co/unsloth/dots.llm1.inst-GGUF

Original weights · Hugging Face

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

huggingface.co/dots-studio/dots.llm1.inst (opens in a new tab)

No sign-in needed.

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

How it’s rated

Quality 53Fair quality (C) · 53 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 7/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 Arduino UNO Q (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.	7.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.	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 score	7.2 / 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 Arduino UNO Q (2 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	66.1 GB	1.2 GB	—	Won't run	53Fair quality (C) · 53 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q3_K_M`	79.0 GB	1.2 GB	—	Won't run	63Good quality (B) · 63 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q4_K_M`	96.1 GB	1.2 GB	—	Won't run	72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q5_K_M`	110 GB	1.2 GB	—	Won't run	73Great quality (A) · 73 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q6_K`	126 GB	1.2 GB	—	Won't run	75Great quality (A) · 75 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`Q8_0`	160 GB	1.2 GB	—	Won't run	76Great quality (A) · 76 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab)
`F16`	295 GB	1.2 GB	—	Won't run	76Great quality (A) · 76 of 100: how capable the model is at F16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (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.

Hardware that can run it

75Great quality (A) · 75 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (256 GB) Q6_K · 37.2 tok/s · Runs great
73Great quality (A) · 73 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. Apple M2 Ultra (192 GB) Q5_K_M · 42.5 tok/s · Runs great
75Great quality (A) · 75 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. Apple M3 Ultra (512 GB) Q6_K · 37.2 tok/s · Runs great
63Good quality (B) · 63 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (128 GB) Q3_K_M · 45.4 tok/s · Runs well (tight fit)
63Good quality (B) · 63 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Q3_K_M · 122 tok/s · Runs well (tight fit)
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GB10 (128 GB) Q4_K_M · 22.2 tok/s · Runs well (tight fit)

Models that do run on the Arduino UNO Q (2 GB)

2Basic quality (D) · 2 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. Falcon-H1 Tiny 90M Instruct Q3_K_M · 42.3 tok/s
2Basic quality (D) · 2 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. SmolLM2 135M Instruct Q2_K · 37.2 tok/s
1Basic quality (D) · 1 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. SmolLM 135M Instruct Q2_K · 37.2 tok/s
7Basic quality (D) · 7 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. LFM2.5 230M Q2_K · 21.0 tok/s
9Basic quality (D) · 9 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. LFM2.5 350M Q2_K · 13.8 tok/s

Quick answers

How much memory does dots.llm1 Instruct need on the Arduino UNO Q 2GB?

Even at Q2_K it needs about 66.1 GB; the Arduino UNO Q 2GB has 1.2 GB usable.

What can the Arduino UNO Q 2GB run instead?

Falcon-H1 Tiny 90M Instruct, SmolLM2 135M Instruct and SmolLM 135M Instruct run best on it; the page lists more, each with its speed.

What hardware can run dots.llm1 Instruct?

M3 Ultra 256GB, M2 Ultra 192GB and M3 Ultra 512GB run it; the page lists more, each with its speed.

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.