Fix FAISS index training and search locking in vector manager #18
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.
This commit addresses two critical issues in
faiss_manager.rs:Missing Index Training: The FAISS index was not being trained before vectors were added. This is a necessary step for many common index types and can cause runtime crashes. The code now correctly trains the index if it is not already trained.
Search Concurrency: The
searchmethod was using a write lock, which unnecessarily prevented concurrent searches. This has been changed to a read lock, significantly improving search throughput under load.PR created automatically by Jules for task 4008945694648760226