zerank-1 small on NVIDIA Jetson AGX Thor (128 GB)
Can the NVIDIA Jetson AGX Thor (128 GB) run zerank-1 small?
Yes, it runs well
Runs well. At Q8_0 it needs about 11.9 GB of 115 GB usable and makes one decision in about 167 ms.
- Best quant
Q8_0- Time per decision
- 167 ms
- Decisions per second
- 6.0/s
- Input assumed
- 512 tokens
- Returns
- Probability or score
Best app to run it on the NVIDIA Jetson AGX Thor (128 GB)
On Linux on ARM boards
- Serves the scoring head directly (rerank, classify or reward) with batching.
vllm serve zeroentropy/zerank-1-small-rerankerDownload zerank-1 small
Original weights · Hugging Face
Full-precision files from ZeroEntropy, for Transformers, Sentence Transformers, Text Embeddings Inference, Infinity or vLLM.
huggingface.co/zeroentropy/zerank-1-small-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 | 36.0 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 11.6 / 15 | |
| Clarity | 15.0 / 15 | |
| Match score | 87.6 / 100 |
Every quantization on the NVIDIA Jetson AGX Thor (128 GB)
| Quant | Memory needed | Available | Speed | Runs | Quality | Download |
|---|---|---|---|---|---|---|
Q4_K_M | 11.1 GB | 115 GB | 162 ms | Runs well | 76Great quality (A) · 76 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. | All files (opens in a new tab) |
Q5_K_M | 11.3 GB | 115 GB | 163 ms | Runs well | 77Great quality (A) · 77 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q6_K | 11.5 GB | 115 GB | 164 ms | Runs well | 79Great quality (A) · 79 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. | All files (opens in a new tab) |
Q8_0 | 11.9 GB | 115 GB | 167 ms | Runs well | 80Great quality (A) · 80 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. | All files (opens in a new tab) |
F16 | 13.5 GB | 115 GB | 179 ms | Runs well | 80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 87/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
-
80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 7900 XTX
-
80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 9070 XT
-
80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
AMD Ryzen AI Max+ 395 (128 GB)
-
80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
Apple M2 Ultra (192 GB)
-
80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
Apple M3 Ultra (256 GB)
-
80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
Apple M3 Ultra (512 GB)
Quick answers
How much memory does zerank-1 small need on the NVIDIA Jetson AGX Thor 128GB?
At Q8_0 it needs about 11.9 GB. The NVIDIA Jetson AGX Thor 128GB has 115 GB usable.
How fast is zerank-1 small on the NVIDIA Jetson AGX Thor 128GB?
It makes one decision in about 167 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.