Skip to content

⚡ Bolt: [performance improvement] Optimize configuration loading for bulk worktree creations#65

Open
Donach wants to merge 1 commit into
cfx/android-hermes-clientfrom
bolt-optimize-config-loading-10500225037097914979
Open

⚡ Bolt: [performance improvement] Optimize configuration loading for bulk worktree creations#65
Donach wants to merge 1 commit into
cfx/android-hermes-clientfrom
bolt-optimize-config-loading-10500225037097914979

Conversation

@Donach
Copy link
Copy Markdown

@Donach Donach commented May 30, 2026

💡 What

Updated WorktreesService.create() to invoke loadConfig() a single time before mapping over array inputs. The loaded configuration is passed to the updated applyWorktreeCreateDefaults method.

🎯 Why

During bulk inserts (via Promise.all + .map()), loadConfig() was being called on every array iteration. Since loadConfig() reads and parses the config.yaml file on every invocation, this resulted in $O(N)$ unnecessary asynchronous disk reads and YAML parsing, dragging down performance significantly as array sizes scale.

📊 Impact

Reduces disk I/O and configuration parsing from $O(N)$ to $O(1)$ for bulk worktree creations. Prevents synchronous blocking (from the Drizzle/DB adapters mapping fast while disk I/O stacks up).

🔬 Measurement

Run pnpm --filter @agor/daemon test -- src/services/worktrees.test.ts to verify backward compatibility and no regressions. The change handles both single object creation and array creation optimally.


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

Move loadConfig() call outside the mapping loop during worktree bulk creation.
This eliminates N-1 redundant disk I/O and YAML parsing operations when
inserting an array of worktrees, reducing operation latency from O(N) to O(1).

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