⚡ Bolt: Optimize NodeModulesScanner concurrency and syscalls#215
⚡ Bolt: Optimize NodeModulesScanner concurrency and syscalls#215
Conversation
Co-authored-by: acebytes <2820910+acebytes@users.noreply.github.com>
|
👋 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. |
|
Closing as duplicate of #216 — same |
Understood. Acknowledging that this work is a duplicate and stopping work on this task. |
💡 What: Marked recursive scanner methods as
nonisolatedand switched toURL.resourceValues(forKeys:).🎯 Why: To prevent TaskGroup tasks from being serialized on the actor's executor and to reduce the number of syscalls when probing file system attributes.
📊 Impact: Substantially faster parallel directory scanning due to unlocked concurrency and unified file system metadata fetching.
🔬 Measurement: Scan operations should complete much faster on directories with large numbers of nested items.
PR created automatically by Jules for task 1323384879870168857 started by @acebytes