RUNLOCALAIv38
->Will it run?Best GPUCompareTroubleshootStartLearnPulseModelsHardwareToolsBench
Run check
RUNLOCALAI

Independently operated catalog for local-AI hardware and software. Hand-written verdicts. Source-cited claims. Reproducible commands when we have them.

OP·Eruo Fredoline
DIR
  • Models
  • Hardware
  • Tools
  • Benchmarks
TOOLS
  • Will it run?
  • Compare hardware
  • Cost vs cloud
  • Choose my GPU
  • Prompting kits
  • Quick answers
REF
  • All buyer guides
  • Learn local AI
  • Methodology
  • Glossary
  • Errors KB
  • Trust
EDITOR
  • About
  • Author
  • How we make money
  • Editorial policy
  • Contact
LEGAL
  • Privacy
  • Terms
  • Sitemap
MAIL · MONTHLY DIGEST
Get monthly local AI changes
Monthly recap. No spam.
DISCLOSURE

Some links on this site are affiliate links (Amazon Associates and other first-class retailers). When you buy through them, we earn a small commission at no extra cost to you. Affiliate links do not influence our verdicts — there are cards we rate highly that we don't have affiliate relationships with, and cards that sell well that we refuse to recommend. Read more →

© 2026 runlocalai.coIndependently operated
RUNLOCALAI · v38
Glossary / Large language models / Reranker (Cross-Encoder)
Large language models

Reranker (Cross-Encoder)

A reranker is a cross-encoder model that scores query/document pairs jointly (concatenated as input), producing a relevance score per pair. Used as a second pass after retrieval: retrieve top-100 by cheap method, rerank to top-10 with the cross-encoder.

Cross-encoders dramatically outperform bi-encoder dense retrieval on relevance — typically +5 to +15 NDCG@10 — because they let the query and document attend to each other. The cost is compute: scoring 100 pairs is 100× slower than the original retrieval.

Common open rerankers: BGE-reranker-v2-m3, Cohere Rerank (API), Jina-Reranker-v2. For local RAG, the m3 family is the standard pick.

Practical example

After hybrid retrieval returns its top 50 candidate chunks for a RAG query, an operator runs BGE-reranker-v2-m3 as a second pass to cut that down to the top 5 actually sent to the LLM's context window. The reranker correctly demotes a chunk that merely shares keywords with the query but discusses an unrelated topic, and promotes a chunk that phrases the answer differently but is clearly the right match — something BM25 and even dense retrieval alone both got wrong in the initial pass. Because cross-encoders score each query-document pair jointly, 50 pairs means 50 forward passes; on a local GPU with a small reranker model this typically adds well under 100ms, which is cheap insurance against feeding the LLM irrelevant context and triggering a hallucinated answer.

Related terms

Embedding (Vector Embedding)Dense RetrievalHybrid Retrieval

Reviewed by Eruo Fredoline. See our editorial policy.

Buyer guides
  • Best GPU for local AI →
  • Best laptop for local AI →
  • Best Mac for local AI →
When it doesn't work
  • CUDA out of memory →
  • Ollama running slowly →
  • ROCm not detected →