zerank-2 on Intel Core Ultra 200H (Arc 140T) (32 GB)

Can the Intel Core Ultra 200H (Arc 140T) (32 GB) run zerank-2?

Yes, but slowly

Slow. At Q8_0 it needs about 6.6 GB of 18.2 GB usable and makes one decision in about 493 ms.

Best quant: Q8_0
Time per decision: 493 ms
Decisions per second: 2.0/s
Input assumed: 512 tokens
Returns: Probability or score

Best app to run it on the Intel Core Ultra 200H (Arc 140T) (32 GB)

On Windows

vLLM

Inference server · runs on vLLM

Serves the scoring head directly (rerank, classify or reward) with batching.
On Windows it runs through WSL2.

vllm serve zeroentropy/zerank-2-reranker

Sentence Transformers Can only use the CPU on this hardware, so it will be slow.

On Linux

vLLM

Inference server · runs on vLLM

Serves the scoring head directly (rerank, classify or reward) with batching.

vllm serve zeroentropy/zerank-2-reranker

Sentence Transformers Can only use the CPU on this hardware, so it will be slow.

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

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)

No sign-in needed.

Links checked 5 hours ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 88Excellent quality (A+) · 88 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q8_0, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Slow: How well it runs on the Intel Core Ultra 200H (Arc 140T) (32 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

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.

PrecisionEditorial precision tier from the model’s published benchmarks, scaled by the quantization or precision used.	39.6 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	25.0 / 25
SpeedTime for one decision against a 100 ms target: reading the input plus any tokens the model writes.	6.8 / 15
ClarityHow easy the answer is to use in code: a probability or score earns the most, written feedback before a score the least.	15.0 / 15
Match score	86.4 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Intel Core Ultra 200H (Arc 140T) (32 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q4_K_M`	4.8 GB	18.2 GB	453 ms	Slow	83Great quality (A) · 83 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.	All files (opens in a new tab)
`Q5_K_M`	5.2 GB	18.2 GB	461 ms	Slow	85Excellent quality (A+) · 85 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.	All files (opens in a new tab)
`Q6_K`	5.7 GB	18.2 GB	471 ms	Slow	87Excellent quality (A+) · 87 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`Q8_0`	6.6 GB	18.2 GB	493 ms	Slow	88Excellent quality (A+) · 88 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking.	All files (opens in a new tab)
`F16`	10.4 GB	18.2 GB	589 ms	Slow	88Excellent quality (A+) · 88 of 100: how capable the model is at F16, whatever it runs on. Match score 85/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 F16 · 48 ms · Runs great
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 F16 · 63 ms · Runs great
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) Q8_0 · 89 ms · Runs great
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 F16 · 99 ms · Runs great
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 Q8_0 · 97 ms · Runs great
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 F16 · 90 ms · Runs great

Quick answers

How much memory does zerank-2 need on the Intel Core Ultra 200H (Arc 140T) 32GB?

At Q8_0 it needs about 6.6 GB. The Intel Core Ultra 200H (Arc 140T) 32GB has 18.2 GB usable.

How fast is zerank-2 on the Intel Core Ultra 200H (Arc 140T) 32GB?

It makes one decision in about 493 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.