GUIDA TECNICA

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.

Ascolta questa guidaNarrato dall'IA · ~3 min

In questa pagina3 minuti di lettura
  1. Panoramica
  2. Immersione profonda
  3. Implementazione nel mondo reale
  4. The Future of Retrieval Metrics: Recall@K, MRR and nDCG
  5. Metterlo in pratica
  6. Continua a esplorare
  7. Domande frequenti

Panoramica

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

Immersione profonda

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.

Implementazione nel mondo reale

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.

Metterlo in pratica

Perché è importante

  • Costo e budget. Le decisioni relative all'architettura determinano prestazioni e costi operativi per anni.
  • Decisioni più chiare. La formazione tecnica aiuta i team a scegliere lo stack giusto, non solo quello più nuovo.
  • Controllo di qualità. Migliori scelte ingegneristiche riducono gli incidenti legati all’affidabilità nella produzione.

Attenzione

  • L'ottimizzazione di un benchmark può nascondere debolezze di sistema più ampie.
  • I costi delle infrastrutture e della manutenzione sono spesso sottostimati.
  • Le lacune in termini di sicurezza e osservabilità possono aumentare man mano che i sistemi diventano più complessi.

Prossimi passi

  1. Definire obiettivi di latenza, qualità e costi prima dell'implementazione.
  2. Benchmark in condizioni di carico e dati realistiche.
  3. Monitoraggio dello strumento per errori, deriva e impatto sull'utente.
  4. Preparare percorsi di rollback e risposta agli incidenti prima della scalabilità.

Continua a esplorare

Newsletter gratuita

Ricevi il briefing quotidiano sull'IA

Tre storie verificate sull'IA ogni mattina nei giorni feriali, scritte in un inglese semplice. Gratuito per sempre, senza pubblicità.

Un'email ogni giorno feriale. Disiscriviti con un clic. Non vendiamo né condividiamo mai il tuo indirizzo.

Mettiti alla prova

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

Feedback immediato su ogni risposta e un certificato condivisibile con un ID verificabile una volta superato un corso.

Inizia il quiz

Sostieni l'istruzione gratuita sull'IA. AI Understanding è un'organizzazione non profit 501(c)(3) — nessun annuncio, nessun paywall, mai. Fai una donazione

Domande frequenti

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.