feat: add configurable batch_size for embedding API calls #114
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.
Problem
Different embedding API providers have different batch size limits:
Currently, MemU processes all embeddings in a single batch, which causes errors when the batch size exceeds the provider's limit.
Solution
This PR adds a configurable
batch_sizeparameter to handle provider-specific limits:Added
batch_sizetoEmbeddingConfigImplemented batch processing in
OpenAIEmbeddingSDKClientUpdated service initialization
batch_sizefrom config to embedding clientChanges
src/memu/app/settings.py: Addbatch_sizefield toEmbeddingConfigsrc/memu/embedding/openai_sdk.py:batch_sizeparameter to__init__embed()methodsrc/memu/app/service.py: Passbatch_sizeto embedding clientExample Usage