feat: parallelize retrieve memories API calls for multiple namespaces to improve latency #163
+41
−22
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.
Description of changes:
retrieve_customer_contextto retrieve memories from multiple namespaces concurrently usingThreadPoolExecutorinstead of sequentiallyretrieve_for_namespacefor cleaner concurrent executionlen(all_context)This improves response time for support queries when multiple namespaces are configured, reducing total retrieval time from the sum of all calls to the maximum of any single call.
Testing:
retrieve_memoriesAPI calls sequentially:retrieve_memoriesAPI calls are made in parallel with the updated code:By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.