GUIDE teknik

Retrieval Metrics: Recall@K, MRR and nDCG

Recall@K measures how many known relevant items appear in the top K results, MRR emphasizes the rank of the first relevant item, and nDCG evaluates ranking quality using graded relevance with position discounts.

Déglul tegtal biiIA-nettali · ~3 min

Ci xët wii3 simili jàng
  1. Résumé
  2. Plongeur bu xóot
  3. Doxal ci àdduna dëgg
  4. The Future of Retrieval Metrics: Recall@K, MRR and nDCG
  5. Teg ko ci jëf
  6. Weyal di banneexu
  7. Laaj yi ñuy faral di laaj

Résumé

Each metric reflects different judgments and use cases, and none directly measures whether a generated answer is correct.

Plongeur bu xóot

Retrieval evaluation starts with queries, a document collection, and relevance judgments. A metric summarizes how a ranked result list compares with those judgments. Recall@K asks what fraction of relevant items appear within the first K results. It is useful when finding all relevant evidence matters, but it ignores the ordering among those retrieved items. Mean reciprocal rank (MRR) scores the rank of the first relevant result: a relevant item at rank one contributes 1, at rank two contributes one-half, and so on; query scores are averaged. This fits tasks where users mainly need one good result near the top. It does not reward additional relevant results after the first. Normalized discounted cumulative gain (nDCG) uses relevance grades and discounts items lower in the ranking. It can distinguish highly relevant from partially relevant documents and rewards placing stronger matches earlier. The exact gain and discount conventions should be documented when comparing implementations. These formulas summarize judged rankings and do not measure answer generation or user satisfaction. These measures depend on a test collection and relevance labels. Incomplete judgments can make a relevant but unjudged result look wrong, and query selection affects conclusions. For retrieval-augmented generation, report retrieval metrics separately from answer-level grounding, correctness, and usefulness. Choose metrics that match the product goal, inspect examples, and evaluate on representative queries rather than selecting whichever score looks largest.

Doxal ci àdduna dëgg

A legal search team uses Recall@20 when it needs to surface most known relevant passages for review.

A help center tracks MRR when users need one useful answer near the top.

A recommender uses graded relevance labels and nDCG to favor stronger matches earlier.

A RAG evaluation reports retrieval recall separately from whether the generated answer is supported.

The Future of Retrieval Metrics: Recall@K, MRR and nDCG

Retrieval systems will increasingly combine lexical, vector, hybrid, and reranking stages, making stage-specific evaluation important. Better relevance judgments and task-aligned graded labels can make nDCG more useful, while user studies can test whether rank gains improve outcomes. RAG evaluation will continue to pair retrieval metrics with answer-level checks. Future benchmarks should publish query sets, judgments, metric settings, and limitations to support meaningful comparisons. Teams should revisit judgments as collections and user needs change over time for all relevant users consistently.

Teg ko ci jëf

Lu tax mu am solo

  • Njëgg ak budget. Dogal yi architecture di jël dañuy indi njariñ ak njëgu liggéey bi ay at ci ginaaw.
  • dogal yu gëna leer. Njàngalem xarala yi dafay jàppale ekip yi ñu tànn li gën, te baña yam ci li gëna bees daal.
  • Xool kalite. Tanneef yu gëna baax ci wàllu ingeñër dina wàññi jafe-jafe yi ci wàllu wóor ci liggéey bi.

Moytul

  • Optimize benn benchmark mën na nëbb ñakk kattan yu gëna yaatu ci sistem bi.
  • Njëg li ñuy fay ci infrastructure yi ak ci toppatoo dañuy faral di suufeel.
  • Bu sistem yi di gëna xawa jafee xam, jafe-jafe yi am ci wàllu kaaraange ak seetlu mën nañu gëna bari.

Jéego yi ci topp

  1. Mandargal latency, kalite, ak njëg yi laata ngay jëfandikoo.
  2. Benchmark ci biir sargal ak done yu dëggu.
  3. Jumtukaay bi di saytu njuumte yi, derive bi ak njeextalu jëfandikukat bi.
  4. Waajal rollback ak yooni tontu ci jafe-jafe yi laata ngay eskale.

Weyal di banneexu

Bulletin bu amul fayda

Jàngal xibaar AI bu bes

Ñatti jaar-jaari IA yuñ firndeel bis bu nekk ci ayu-bis bi, ñu bind leen ci Àngle bu leer. Gratis ba fàww, amul yëgle.

Benn email bis bu nekk ci ayu-bis bi. Benn klik nga dindi abonemaa bi. Dunu musa jaay wala séddoo sa adres.

Nattal sa bopp

Take the Retrieval Metrics: Recall@K, MRR and nDCG quiz

Feedback ci saasi ci bépp tontu, ak sertifikaa buñ mëna séddoo ak ID buñ mëna saytu soo jàllee ci njàng mi.

Tambalil quiz

Jàppale njàngum IA te doo fay. AI Understanding mbootaay la buy def te Yàlla tax — amul yëgle, amul paywall, musul am. Defal ab sarax

Laaj yi ñuy faral di laaj

What is Retrieval Metrics: Recall@K, MRR and nDCG?

Recall@K measures how many known relevant items appear in the top K results, MRR emphasizes the rank of the first relevant item, and nDCG evaluates ranking quality using graded relevance with position discounts. Each metric reflects different judgments and use cases, and none directly measures whether a generated answer is correct.

What does Recall@K measure?

Recall at a cutoff measures relevant-item coverage in the top K.

What does Recall@K fail to distinguish by itself?

Recall@K measures coverage at the cutoff, not ordering within those results.

Why can incomplete relevance judgments distort retrieval metrics?

Metrics depend on the judged collection and can penalize unjudged positives.

Does a high retrieval Recall@K prove that a RAG answer is correct?

Retrieval and answer generation are distinct evaluation stages.