⚡ Bolt: Parallelize bulk cache deletion using TaskGroup sliding window#252
⚡ Bolt: Parallelize bulk cache deletion using TaskGroup sliding window#252acebytes wants to merge 1 commit into
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. |
💡 What: Refactored
removeContentsto usewithThrowingTaskGroupwith a sliding window approach (maxConcurrency = 8) and made it anonisolated async throwsmethod with an injectedFileManager.🎯 Why: Previous implementation deleted directory contents sequentially on the actor's executor, causing slow, serialized disk I/O when cleaning caches with thousands of files. The
TaskGroupsecurely parallelizes file deletion and retains original fail-fast semantics without legacy GCD or custom locks.📊 Impact: Substantially speeds up cache deletion by parallelizing
FileManager.removeItemcalls safely within Swift's structured concurrency model.🔬 Measurement: Observe faster cleanup times for large cache directories (e.g., Xcode DerivedData) in the application.
PR created automatically by Jules for task 9515336209934025715 started by @acebytes