-
Notifications
You must be signed in to change notification settings - Fork 1
β‘ Bolt: Stream indexing results with concurrent task pool #405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
AhmmedSamier
wants to merge
1
commit into
master
Choose a base branch
from
bolt/indexer-worker-concurrency-985315326601958411
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π§© Analysis chain
π Script executed:
Repository: AhmmedSamier/DeepLens
Length of output: 1818
π Script executed:
Repository: AhmmedSamier/DeepLens
Length of output: 2624
π Script executed:
Repository: AhmmedSamier/DeepLens
Length of output: 695
π Script executed:
Repository: AhmmedSamier/DeepLens
Length of output: 146
Replace the eager map/limit pattern with a pull-based runner pool to bound memory allocation.
The code violates two guidelines:
Type safety: Line 39 uses
any[]forbatchItems. This removes type safety from the worker-to-parent message contract and contradicts the guideline "Ensure no newanytypes are introduced during development". Use an explicit type (e.g.,SymbolInfo[]or appropriate item type from the parser).Memory efficiency:
filePaths.map(limit(...))creates a closure and promise for every file upfront, even though onlyCONCURRENCY(15) tasks run concurrently. When a worker receives 200+ files (e.g.,getWorkerChunkSizereturns 60 for batches β₯200), this allocates ~200 closures that remain queued in memory. A pull-based model that spawns only 15 runners pulling files one-by-one keeps queue size O(CONCURRENCY) and reduces GC pressure in this hot path.The suggested implementation spawns exactly
Math.min(CONCURRENCY, filePaths.length)runners, each polling the next file index until exhausted, rather than eagerly mapping all files.π€ Prompt for AI Agents