⚡ Bolt: [parallelize cache directory cleanup]#251
Conversation
Converted the sequential `removeContents` method in `CacheCleaner` to an `async nonisolated` method that deletes directory contents concurrently using a `withThrowingTaskGroup` (sliding window capped at 8 workers). 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. |
Understood. Acknowledging that this work is a duplicate of #257 and stopping work on this task. |
💡 What: Converted the sequential
removeContentsmethod inCacheCleanerto anasync nonisolatedmethod that deletes directory contents concurrently using awithThrowingTaskGroup(sliding window capped at 8 workers).🎯 Why: Cache directories (like Xcode DerivedData) can contain hundreds of subdirectories. Deleting them sequentially is slow and creates an I/O bottleneck. Parallelizing
FileManager.removeItemspeeds up the permanent deletion process significantly.📊 Impact: Reduces cleanup time for large cache categories (like npm, CocoaPods, Xcode DerivedData) by running deletions concurrently.
🔬 Measurement: Verify by clearing a large Xcode DerivedData directory and measuring the time it takes compared to the previous sequential implementation.
PR created automatically by Jules for task 6086645156081242781 started by @acebytes