NuExtract 2.0 4B on NVIDIA GeForce RTX 4080 SUPER
Can the NVIDIA GeForce RTX 4080 SUPER run NuExtract 2.0 4B?
Yes, it runs great
Runs great. At Q4_K_M it needs about 3.8 GB of 16.0 GB usable and makes one decision in about 129 ms.
- Best quant
Q4_K_M- Time per decision
- 129 ms
- Decisions per second
- 7.7/s
- Input assumed
- 256 tokens
- Returns
- Labeled spans or fields
Best app to run it on the NVIDIA GeForce RTX 4080 SUPER
On Windows
- Point-and-click: search, download and chat in one window.
On Linux
- Point-and-click: search, download and chat in one window.
Download NuExtract 2.0 4B
Recommended for the NVIDIA GeForce RTX 4080 SUPER: Q4_K_M. 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 Q4_K_M file (opens in a new tab)
huggingface.co/numind/NuExtract-2.0-4B-GGUF (opens in a new tab)
ollama run hf.co/numind/NuExtract-2.0-4B-GGUF:Q4_K_MOriginal 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 | 32.5 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 13.2 / 15 | |
| Clarity | 13.0 / 15 | |
| Match score | 83.7 / 100 |
Every quantization on the NVIDIA GeForce RTX 4080 SUPER
| Quant | Memory needed | Available | Time per decision | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q4_K_M | 3.8 GB | 16.0 GB | 129 ms | Runs great | 72Great quality (A) · 72 of 100: how capable the model is at Q4_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) |
Q5_K_M | 4.1 GB | 16.0 GB | 150 ms | Runs well | 73Great quality (A) · 73 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 | 4.6 GB | 16.0 GB | 173 ms | Runs well | 75Great quality (A) · 75 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q8_0 | 5.5 GB | 16.0 GB | 225 ms | Runs well | 76Great quality (A) · 76 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
F16 | 9.0 GB | 16.0 GB | 454 ms | Slow | 76Great quality (A) · 76 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
-
76Great quality (A) · 76 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5090
-
76Great quality (A) · 76 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
73Great quality (A) · 73 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4090
-
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5080
-
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 7900 XTX
-
72Great quality (A) · 72 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5070 Ti
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.