Apertus v1.5 70B on Intel Xeon W-2100 series NAS (64 GB)
Can the Intel Xeon W-2100 series NAS (64 GB) run Apertus v1.5 70B?
Barely: it runs very slowly (tight fit)
Very slow (tight fit). At Q4_K_M it needs about 51.6 GB of 54.4 GB usable, with an estimated speed of 0.9 tok/s.
- Best quant
Q4_K_M- Generation speed
- 0.9 tok/s
- Prompt processing
- 5.0 tok/s
- First token (1K prompt)
- 204.8 s
- Largest safe context
- 16K
Download Apertus v1.5 70B
Original weights · Hugging Face
Full-precision files from Swiss AI, for fine-tuning, vLLM, Transformers.
huggingface.co/swiss-ai/Apertus-v1.5-70B (opens in a new tab)
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.
| Model quality | 28.2 / 45 | |
|---|---|---|
| Memory fit | 24.0 / 25 | |
| Speed | 2.3 / 15 | |
| Memory use | 15.0 / 15 | |
| Match score | 69.5 / 100 |
Every quantization on the Intel Xeon W-2100 series NAS (64 GB)
| Quant | Memory needed | Available | Speed | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q2_K | 36.4 GB | 54.4 GB | 1.5 tok/s | Very slow | 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q3_K_M | 42.9 GB | 54.4 GB | 1.2 tok/s | Very slow | 55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q4_K_M | 51.6 GB | 54.4 GB | 0.9 tok/s | Very slowtight fit | 62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q5_K_M | 58.8 GB | 54.4 GB | 0.6 tok/s | Very slowover memory limit | 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q6_K | 66.7 GB | 54.4 GB | — | Won't run | 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q8_0 | 84.0 GB | 54.4 GB | — | Won't run | 66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
F16 | 152 GB | 54.4 GB | — | Won't run | 66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 8/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
-
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking.
Apple M4 Max (64 GB)
-
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking.
Apple M2 Ultra (192 GB)
-
62Good quality (B) · 62 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.
Apple M3 Ultra (256 GB)
-
55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking.
Apple M4 Max (128 GB)
-
62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking.
Apple M3 Ultra (512 GB)
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.