Improve memory efficiency and resource cleanup #224
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
This PR improves memory efficiency and resource cleanup across ingestion/query flows by avoiding quadratic string building, reducing peak allocations, and ensuring database/client resources are properly released.
Motivation
The API can process large uploads and many chunks per file. A few code paths could retain resources (clients/pools) across restarts or build large intermediate strings/buffers. This PR focuses on reducing peak RAM and preventing resource retention without changing the public API.
What changed
main.pyapp/services/mongo_client.pyapp/services/vector_store/factory.pyapp/services/vector_store/extended_pg_vector.pyapp/services/vector_store/atlas_mongo_vector.pyapp/utils/document_loader.pyapp/routes/document_routes.pytests/services/test_vector_store.pyNotes
Checklist