fix(config): reduce default reranker_max_candidates from 300 to 50 (#2554)#2796
Closed
handnewb wants to merge 1 commit into
Closed
fix(config): reduce default reranker_max_candidates from 300 to 50 (#2554)#2796handnewb wants to merge 1 commit into
handnewb wants to merge 1 commit into
Conversation
The default of 300 reranker candidates causes 30s+ recall latency for the common case. Most reranker providers are optimized for batches of 50-100 documents. 50 is a safer default that avoids the latency cliff while still providing enough candidates for good recall quality. Operators who need larger batches can set HINDSIGHT_API_RERANKER_MAX_CANDIDATES explicitly. Closes vectorize-io#2554
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The default
reranker_max_candidates=300causes 30s+ recall latency because most reranker providers are optimized for batches of 50-100 documents, not 300. This latency cliff affects all users who don't explicitly configure this value.Changes
DEFAULT_RERANKER_MAX_CANDIDATESfrom 300 to 50Operators who need larger batches can set
HINDSIGHT_API_RERANKER_MAX_CANDIDATESexplicitly.Closes #2554