Skip to content

⚡ Bolt: Optimize frontend search filtering via useFetch transform#65

Open
subsubl wants to merge 1 commit intomasterfrom
bolt-optimize-frontend-filtering-11003280806529398135
Open

⚡ Bolt: Optimize frontend search filtering via useFetch transform#65
subsubl wants to merge 1 commit intomasterfrom
bolt-optimize-frontend-filtering-11003280806529398135

Conversation

@subsubl
Copy link
Copy Markdown
Owner

@subsubl subsubl commented Mar 16, 2026

💡 What: Added a transform function to the /api/apps useFetch call in pages/index.vue. This function pre-computes lowercased _searchName and _searchDesc properties on the app objects. The filteredApps computed property was then updated to use these pre-computed fields instead of calling .toLowerCase() on every iteration.
🎯 Why: The reactive filteredApps computed property previously called .toLowerCase() on the name and description of every single app during its .filter() loop. Since this computed property is re-evaluated frequently when the search input changes, it allocates numerous temporary strings and causes unnecessary CPU/Garbage Collection overhead, scaling poorly with the number of apps.
📊 Impact: Reduces memory allocation to O(1) per keystroke instead of O(N), speeding up search filtering and preventing GC spikes, making the UI noticeably snappier for large app lists.
🔬 Measurement: Verify by typing rapidly in the search input on the homepage (/) and observing the search functionality. You can also run a CPU profile during search to observe the reduction in string allocation and GC events.


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

Pre-computes search strings (_searchName, _searchDesc) in the `useFetch` transform to avoid O(N) `.toLowerCase()` allocations per keystroke in the computed property.

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