on

Can the Apple M2 (16 GB) run Jina Reranker v3?

84Great quality (A) · 84 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.

Yes, it runs well

Runs well. At Q8_0 it needs about 2.3 GB of 10.7 GB usable and makes one decision in about 153 ms.

Best quant
Q8_0
Time per decision
153 ms
Decisions per second
6.5/s
Input assumed
512 tokens
Returns
Probability or score

Best app to run it on the Apple M2 (16 GB)

On macOS

llama.cpp

Command line + local API · runs on llama.cpp

  • Serves the GGUF build behind a /v1/rerank endpoint with llama-server --rerank.
llama-server -hf jinaai/jina-reranker-v3-GGUF:Q8_0 --rerank
  • Sentence Transformers A few lines of Python with Transformers or Sentence Transformers; easiest for scripts and notebooks.
  • Lemonade Serves the GGUF build behind a /v1/rerank endpoint with llama-server --rerank.

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 Jina Reranker v3

Recommended for the Apple M2 (16 GB): Q8_0. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in llama.cpp (llama-server --rerank), Lemonade and other llama.cpp servers with a rerank endpoint. No sign-in needed.

Download the Q8_0 file (opens in a new tab)

huggingface.co/jinaai/jina-reranker-v3-GGUF (opens in a new tab)

llama-server -hf jinaai/jina-reranker-v3-GGUF:Q8_0 --rerank

Original weights · Hugging Face

Full-precision files from Jina AI, for Transformers, Sentence Transformers, Text Embeddings Inference, Infinity or vLLM.

huggingface.co/jinaai/jina-reranker-v3 (opens in a new tab)

No sign-in needed.

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 84Great quality (A) · 84 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.
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 Runs well
How well it runs on the Apple M2 (16 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.37.8 / 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.12.1 / 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 score89.9 / 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 Apple M2 (16 GB)

Quant Memory needed Available Speed Runs Quality Download
Q4_K_M 2.1 GB 10.7 GB 147 ms Runs well 79Great quality (A) · 79 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 2.1 GB 10.7 GB 149 ms Runs well 81Great quality (A) · 81 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. GGUF (opens in a new tab)
Q6_K 2.2 GB 10.7 GB 150 ms Runs well 83Great quality (A) · 83 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 2.3 GB 10.7 GB 153 ms Runs well 84Great quality (A) · 84 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. GGUF (opens in a new tab)
F16 2.9 GB 10.7 GB 166 ms Runs well 84Great quality (A) · 84 of 100: how capable the model is at F16, whatever it runs on. Match score 89/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 512-token input and about 1 tokens written. Batching servers process many requests at once.

Other hardware that runs it

Quick answers

How much memory does Jina Reranker v3 need on the M2 16GB?

At Q8_0 it needs about 2.3 GB. The M2 16GB has 10.7 GB usable.

How fast is Jina Reranker v3 on the M2 16GB?

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

Was this page helpful?