Short answer: build a small, versioned evaluation set from real documentation questions, score retrieval with recall@k and ranking quality, then choose the fastest index that clears your relevance threshold. For a logistics team watching a carrier web page, keep latency as a constraint, not as a substitute for finding the paragraph that explains the change.
Retrieval approach Pick it when Watch for
Lexical search (BM25) Error codes, route names, and exact terms dominate Synonyms and paraphrases can be missed
Vector search Engineers ask concept-shaped questions across varied wording Similar-sounding passages can outrank the answer
Hybrid search Queries mix identifiers with natural language Two scores need a repeatable fusion rule
The evaluation set is the control surface. Without it, a new embedding model or chunk size is only a feeling in a dashboard.…