Optimize sequential namespace search using asyncio.gather#73
Optimize sequential namespace search using asyncio.gather#73ishaanxgupta wants to merge 2 commits intomainfrom
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
lgtm @ved015 have a look |
|
lgtm please merge it |
What: Optimized sequential namespace searches in
_search_symbolsand_search_filesinsrc/pipelines/code_retrieval.pyusingasyncio.gather.Why: The codebase iterated over
self.reposand awaited a separate asynchronous namespace search sequentially for each repository. This caused latency to scale linearly with the number of repositories searched. Usingasyncio.gatherexecutes these searches concurrently.Impact: Significant reduction in latency for multi-repository code queries.
Measurement: In local mocked benchmarking with an artificial 100ms latency per namespace search and 10 configured repositories, query times dropped from 2.01 seconds to 0.20 seconds per call.
PR created automatically by Jules for task 6874361935615458554 started by @ishaanxgupta