Why architecture matters here

Reranker fails on latency + wrong model choice. Architecture matters because retriever + cross-encoder + LLM compose.

Advertisement

The architecture: every piece explained

The top strip is pipeline. Query. Retriever. Candidate list. Cross-encoder.

The middle row is output. Relevance score. Top-k final. LLM answer. Latency budget.

The lower rows are ops. Cache. Metrics. Ops — model choice + batch + hardware.

LLM reranker — cross-encoder + candidate list + relevanceimprove retrieval precision after recallQueryuser textRetrieverbi-encoder top-kCandidate list50-200 docsCross-encoderquery + doc scoreRelevance scoreper pairTop-k finalafter rerankLLM answerwith contextLatency budgetreranker costCache reranker scoreshot pairsMetricsnDCG + MRROps — model choice + batch + hardwarescorerankanswerbudgetreusewatchwatchoperateoperate
LLM reranker: cross-encoder over retriever candidates.
Advertisement

End-to-end flow

End-to-end: query in. Retriever gets top-100 in 30ms. Cross-encoder scores each pair in batch — 200ms. Top-5 pass to LLM. Total pre-LLM latency ~250ms.