on

Can the Arduino UNO Q (4 GB) run NuExtract 2.0 2B?

69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.

Barely: it runs very slowly (tight fit)

Very slow (tight fit). At Q6_K it needs about 2.7 GB of 2.8 GB usable and makes one decision in about 99.6 s.

Best quant
Q6_K
Time per decision
99.6 s
Decisions per second
0.0/s
Input assumed
256 tokens
Returns
Labeled spans or fields

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

On Linux on ARM boards

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open NuExtract 2.0 2B in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

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 NuExtract 2.0 2B

Recommended for the Arduino UNO Q (4 GB): Q6_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 Q6_K file (opens in a new tab)

huggingface.co/numind/NuExtract-2.0-2B-GGUF (opens in a new tab)

ollama run hf.co/numind/NuExtract-2.0-2B-GGUF:Q6_K

Original weights · Hugging Face

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

huggingface.co/numind/NuExtract-2.0-2B (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 69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q6_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 Very slowtight fit
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.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.31.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.24.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.0.5 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.13.0 / 15
Match score68.7 / 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
Q4_K_M 2.2 GB 2.8 GB 91.7 s Very slow 66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 2.5 GB 2.8 GB 95.5 s Very slowtight fit 67Good quality (B) · 67 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 2.7 GB 2.8 GB 99.6 s Very slowtight fit 69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 3.2 GB 2.8 GB 115.3 s Very slowfar over memory limit 70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 48/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 5.3 GB 2.8 GB — Won't run 70Great quality (A) · 70 of 100: how capable the model is at F16, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Times are for one request with a 256-token input and about 24 tokens written. Batching servers process many requests at once.

Other hardware that runs it

Quick answers

How much memory does NuExtract 2.0 2B need on the Arduino UNO Q 4GB?

At Q6_K it needs about 2.7 GB. The Arduino UNO Q 4GB has 2.8 GB usable.

How fast is NuExtract 2.0 2B on the Arduino UNO Q 4GB?

It makes one decision in about 99.6 s at Q6_K, an estimate from the hardware and the size of the model.

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?