Skip to content

⚡ Bolt: [performance improvement]#87

Draft
raccioly wants to merge 1 commit intomainfrom
bolt-perf-shared-ignore-cache-10162582963630816006
Draft

⚡ Bolt: [performance improvement]#87
raccioly wants to merge 1 commit intomainfrom
bolt-perf-shared-ignore-cache-10162582963630816006

Conversation

@raccioly
Copy link
Copy Markdown
Owner

@raccioly raccioly commented May 6, 2026

💡 What: Implemented a memoization cache (filterCache) within cli/shared-ignore.mjs for the buildIgnoreFilter function. It uses the stringified patterns array as a cache key to avoid redundant regular expression compilation.

🎯 Why: During directory traversal, validators repeatedly construct ignore filters with identical config arrays. Calling globToRegex and mapping the patterns into RegExp objects inside tight recursive loops caused an O(N*M) performance bottleneck, as seen in the benchmarking script (perf-test-shared-ignore.mjs) taking ~784ms for 100k iterations.

📊 Impact: The execution time of identical ignore filter setups was reduced by roughly ~88% in micro-benchmarks (down from ~784ms to ~94ms for 100k invocations). This provides a measurable speedup during deep recursive scans across the entire CLI validation lifecycle.

🔬 Measurement: The improvement was verified via a custom Node.js timing script that simulated repetitive shouldIgnore calls and by running the full test suite (pnpm test), ensuring zero functional regressions for ignored files.


PR created automatically by Jules for task 10162582963630816006 started by @raccioly

Co-authored-by: raccioly <63126795+raccioly@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