Skip to content

⚡ Bolt: Cache loadConfig during bulk worktree creations#101

Open
Donach wants to merge 1 commit into
cfx/android-hermes-clientfrom
bolt-optimization-worktrees-load-config-8690505536526889028
Open

⚡ Bolt: Cache loadConfig during bulk worktree creations#101
Donach wants to merge 1 commit into
cfx/android-hermes-clientfrom
bolt-optimization-worktrees-load-config-8690505536526889028

Conversation

@Donach

@Donach Donach commented Jun 23, 2026

Copy link
Copy Markdown

💡 What: Hoisted the loadConfig() call outside the bulk creation loop in the WorktreesService and passed the AgorConfig to the helper function.
🎯 Why: To eliminate an O(N) disk I/O performance bottleneck where the configuration was being parsed from disk on every iteration of a bulk operation.
📊 Impact: Reduces file system operations to O(1) during bulk worktree creations. This will significantly decrease latency when initializing many worktrees at once.
🔬 Measurement: Verify by running pnpm --filter @agor/daemon test to ensure WorktreesService creation flows behave exactly as before but with improved theoretical performance over large data sets.


PR created automatically by Jules for task 8690505536526889028 started by @Donach

This commit addresses a performance bottleneck in `apps/agor-daemon/src/services/worktrees.ts`. During bulk worktree creation, `loadConfig()` was being called inside a `Promise.all` loop for every item. Because `loadConfig()` performs synchronous disk I/O, this resulted in an O(N) I/O bottleneck.

The optimization hoists `loadConfig()` outside the loop. It is loaded exactly once and passed as an argument to the configuration handler, achieving O(1) disk I/O.

Co-authored-by: Donach <39565367+Donach@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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