zerank-2 on Apple M5 Max (36 GB)
Can the Apple M5 Max (36 GB) run zerank-2?
Yes, it runs well
Runs well. At Q8_0 it needs about 7.1 GB of 24.1 GB usable and makes one decision in about 240 ms.
- Best quant
Q8_0- Time per decision
- 240 ms
- Decisions per second
- 4.2/s
- Input assumed
- 512 tokens
- Returns
- Probability or score
Best app to run it on the Apple M5 Max (36 GB)
On macOS
- A few lines of Python with Transformers or Sentence Transformers; easiest for scripts and notebooks.
python -c "from sentence_transformers import CrossEncoder; print(CrossEncoder('zeroentropy/zerank-2-reranker').predict([('query', 'document')]))"Download zerank-2
Original weights · Hugging Face
Full-precision files from ZeroEntropy, for Transformers, Sentence Transformers, Text Embeddings Inference, Infinity or vLLM.
huggingface.co/zeroentropy/zerank-2-reranker (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.
| Precision | 39.6 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 9.7 / 15 | |
| Clarity | 15.0 / 15 | |
| Match score | 89.3 / 100 |
Every quantization on the Apple M5 Max (36 GB)
| Quant | Memory needed | Available | Speed | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q4_K_M | 5.3 GB | 24.1 GB | 232 ms | Runs well | 83Great quality (A) · 83 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q5_K_M | 5.7 GB | 24.1 GB | 234 ms | Runs well | 85Excellent quality (A+) · 85 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. | All files (opens in a new tab) |
Q6_K | 6.1 GB | 24.1 GB | 236 ms | Runs well | 87Excellent quality (A+) · 87 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. | All files (opens in a new tab) |
Q8_0 | 7.1 GB | 24.1 GB | 240 ms | Runs well | 88Excellent quality (A+) · 88 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
F16 | 10.9 GB | 24.1 GB | 259 ms | Runs well | 88Excellent quality (A+) · 88 of 100: how capable the model is at F16, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Times are for one request with a 512-token input and about 1 tokens written. Batching servers process many requests at once.
Other hardware that runs it
-
88Excellent quality (A+) · 88 of 100: how capable the model is at F16, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 7900 XTX
-
88Excellent quality (A+) · 88 of 100: how capable the model is at F16, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 9070 XT
-
88Excellent quality (A+) · 88 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking.
AMD Ryzen AI Max+ 395 (128 GB)
-
88Excellent quality (A+) · 88 of 100: how capable the model is at F16, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 3090
-
88Excellent quality (A+) · 88 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4070 SUPER
-
88Excellent quality (A+) · 88 of 100: how capable the model is at F16, whatever it runs on. Match score 94/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4070 Ti SUPER
Quick answers
How much memory does zerank-2 need on the M5 Max 36GB?
At Q8_0 it needs about 7.1 GB. The M5 Max 36GB has 24.1 GB usable.
How fast is zerank-2 on the M5 Max 36GB?
It makes one decision in about 240 ms at Q8_0, 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.