Skip to content

⚡ Bolt: [performance improvement]#68

Open
subsubl wants to merge 1 commit intomasterfrom
bolt/perf-builder-array-from-18071276563080266221
Open

⚡ Bolt: [performance improvement]#68
subsubl wants to merge 1 commit intomasterfrom
bolt/perf-builder-array-from-18071276563080266221

Conversation

@subsubl
Copy link
Copy Markdown
Owner

@subsubl subsubl commented Mar 19, 2026

💡 What: Replaced Array.from(filesMap.value.entries()).find() with a standard for...of loop in pages/builder.vue when searching for appinfo.spixi and icon.png files.

🎯 Why: Array.from(map.entries()) creates a new array in memory every time it's called, causing an O(N) memory allocation and subsequent garbage collection pressure, particularly when large Spixi mini apps are loaded. The for...of loop iterates lazily over the map and allows for an early break, significantly reducing the memory footprint.

📊 Impact: Avoids unnecessary O(N) intermediate array allocation and allows O(1) early exit when a matched file is found, improving performance on systems processing large zip folders.

🔬 Measurement: Build and functionally test the builder.vue packing process. Observe reduced memory utilization over time compared to the array-mapping alternative.


PR created automatically by Jules for task 18071276563080266221 started by @subsubl

Replaces `Array.from(map.entries()).find()` with an O(1) iterative `for...of` loop in `pages/builder.vue` to avoid intermediate O(N) array allocation overhead and garbage collection pressure when performing case-insensitive file lookups.

Co-authored-by: subsubl <114085822+subsubl@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