Skip to content

⚡ Bolt: [performance improvement] Offload blocking I/O off the @MainActor#41

Open
acebytes wants to merge 1 commit intomainfrom
bolt/optimize-blocking-io-mainactor-4555539010936744612
Open

⚡ Bolt: [performance improvement] Offload blocking I/O off the @MainActor#41
acebytes wants to merge 1 commit intomainfrom
bolt/optimize-blocking-io-mainactor-4555539010936744612

Conversation

@acebytes
Copy link
Copy Markdown
Contributor

💡 What: Refactored CacheoutViewModel to offload synchronous, blocking operations like DiskInfo.current(), Process execution, waitUntilExit(), and readDataToEndOfFile() off the @MainActor by using Task.detached { ... }.value.

🎯 Why: Executing these I/O-heavy blocking operations on the @MainActor blocked the main thread. This causes UI hitching or unresponsiveness while waiting for file system attributes to be read or external shell processes (like docker system prune) to exit.

📊 Impact: Greatly improves UI responsiveness by preventing the main thread from stalling. Heavy synchronous I/O operations are correctly dispatched to the background concurrent pool.

🔬 Measurement: Verify that the main UI remains perfectly responsive and smooth while running the scan process or running "Docker prune" from the menubar, especially when the file system is slow or the docker prune process takes seconds to finish.


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

- Wrapped `DiskInfo.current()`, `Process` execution, `waitUntilExit()`, and `Pipe` reads inside `Task.detached { ... }` in `CacheoutViewModel`.
- This ensures these synchronous blocking I/O calls run on the background concurrent pool rather than blocking the main UI thread.
- Results are safely awaited and assigned back to the `@MainActor` variables (`diskInfo` and `lastDockerPruneResult`).

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