refactor: Async batch processing, limits, and configuration #80
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.
Added async api calls to embed (process) and add chunks (documents) to vector storage.
Added env variables:
MAX_CHUNKS
,EMBEDDING_TIMEOUT
,BATCH_SIZE
, andCONCURRENT_LIMIT
to configure/limit batching api class. Description in Readme.Tested with PGVector with bedrock and
amazon.titan-embed-text-v2:0
. Also rebuilt in docker successfully.BATCH_SIZE
andCONCURRENT_LIMIT
affecting process calls to embed correctlyMAX_CHUNKS
works as limit and throws exception if over. Correct default behavior of ignoringEMBEDDING_TIMEOUT
works within limit and throws exception if over