NuExtract 2.0 2B on AMD Radeon RX 7900 XTX
Can the AMD Radeon RX 7900 XTX run NuExtract 2.0 2B?
Yes, it runs great
Runs great. At Q6_K it needs about 3.7 GB of 24.0 GB usable and makes one decision in about 87 ms.
- Best quant
Q6_K- Time per decision
- 87 ms
- Decisions per second
- 12/s
- Input assumed
- 256 tokens
- Returns
- Labeled spans or fields
Best app to run it on the AMD Radeon RX 7900 XTX
On Windows
- AMD’s own app: llama.cpp tuned for Radeon on Vulkan and ROCm.
lemonade pull numind/NuExtract-2.0-2B-GGUF:Q6_KDownload NuExtract 2.0 2B
Recommended for the AMD Radeon RX 7900 XTX: 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_KOriginal weights · Hugging Face
Full-precision files from NuMind, for fine-tuning, vLLM, Transformers.
How it’s rated
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.
| Precision | 31.2 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 15.0 / 15 | |
| Clarity | 13.0 / 15 | |
| Match score | 84.2 / 100 |
Every quantization on the AMD Radeon RX 7900 XTX
| Quant | Memory needed | Available | Time per decision | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q4_K_M | 3.2 GB | 24.0 GB | 64 ms | Runs great | 66Good quality (B) · 66 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. | GGUF (opens in a new tab) |
Q5_K_M | 3.4 GB | 24.0 GB | 75 ms | Runs great | 67Good quality (B) · 67 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q6_K | 3.7 GB | 24.0 GB | 87 ms | Runs great | 69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q8_0 | 4.2 GB | 24.0 GB | 114 ms | Runs great | 70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
F16 | 6.3 GB | 24.0 GB | 234 ms | Runs well | 70Great quality (A) · 70 of 100: how capable the model is at F16, whatever it runs on. Match score 79/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
-
70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4090
-
70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5090
-
70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 3090
-
69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5070 Ti
-
69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5080
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.