increase embedding batch size from 50 to 500#86
Merged
Conversation
The proxy already accepts up to 500 items per request and sub-batches to the upstream API at 100 internally. Sending larger batches from the server reduces proxy round-trips from ~400 to ~40 on a cold EIP embed.
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
1 participant
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.
Bumps the client-side embedding batch size to match the proxy's 500-item hard cap. The proxy already sub-batches to the upstream API at 100 internally, so this just cuts the number of round-trips on cold starts from ~400 to ~40.