Skip to content

⚡ Bolt: Fix task serialization in scanners for true parallelism#75

Open
acebytes wants to merge 1 commit intomainfrom
bolt-fix-task-serialization-13518718015767671395
Open

⚡ Bolt: Fix task serialization in scanners for true parallelism#75
acebytes wants to merge 1 commit intomainfrom
bolt-fix-task-serialization-13518718015767671395

Conversation

@acebytes
Copy link
Copy Markdown
Contributor

@acebytes acebytes commented Apr 3, 2026

💡 What: Refactored CacheScanner and NodeModulesScanner from actor to struct.

🎯 Why: In Swift structured concurrency, using an actor to manage a withTaskGroup where tasks invoke synchronous, blocking I/O (like FileManager operations) directly on the actor inadvertently serializes the tasks, preventing parallelism. Since these components are stateless and only interact with thread-safe dependencies (FileManager.default), converting them to struct allows child tasks to execute concurrently across the global thread pool, unblocking the performance bottleneck.

📊 Impact: Allows actual concurrent execution for filesystem scanning. Expect significant speedups during cache and node_modules scans, especially in I/O bound situations.

🔬 Measurement: Observe the scan times for both general caches and node_modules; the time to complete should reflect concurrent execution rather than sequential processing.

(Note: Added a journal entry to .jules/bolt.md documenting the learning around Swift actor serialization and sync I/O).


PR created automatically by Jules for task 13518718015767671395 started by @acebytes

- Changed `CacheScanner` and `NodeModulesScanner` from `actor` to `struct`
- Updated docstrings to reflect the thread-safety architecture
- By avoiding actor isolation for these stateless components, their `withTaskGroup` implementations can now execute parallel filesystem scanning across multiple threads without being serialized to the actor's context.

Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant