Skip to content

⚡ Bolt: [performance improvement] optimize array filtering#191

Draft
yeboster wants to merge 1 commit intomainfrom
bolt-optimize-array-filtering-13012399804257829172
Draft

⚡ Bolt: [performance improvement] optimize array filtering#191
yeboster wants to merge 1 commit intomainfrom
bolt-optimize-array-filtering-13012399804257829172

Conversation

@yeboster
Copy link
Copy Markdown
Contributor

💡 What:
Converted arrays to Sets before performing lookup in filter() loops in the voters/add and voters/remove endpoints.

🎯 Why:
The previous implementation used .includes() inside .filter(), which is an O(N * M) operation. Converting the lookup array to a Set first reduces this to O(N).

📊 Impact:
Reduces the time complexity of finding voters to add or remove from quadratic to linear. This improves performance, particularly as the number of total owners and voters grows into the tens of thousands.

🔬 Measurement:
This improves performance, particularly as the number of total owners and voters grows. Node.js benchmark: Array.includes takes ~2.805s vs Set.has takes ~18.429ms for arrays with 50000 and 10000 items.


PR created automatically by Jules for task 13012399804257829172 started by @yeboster

What: Converted arrays to Sets before performing lookup in `filter()` loops in the `voters/add` and `voters/remove` endpoints.
Why: The previous implementation used `.includes()` inside `.filter()`, which is an O(N * M) operation. Converting to a Set first reduces this to O(N).
Impact: Reduces the time complexity of finding voters to add or remove from quadratic to linear.
Measurement: This improves performance, particularly as the number of total owners and voters grows into the tens of thousands. Node.js benchmark: Array.includes takes ~2.805s vs Set.has takes ~18.429ms for large arrays.

Co-authored-by: yeboster <23556525+yeboster@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.

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app Ready Ready Preview, Comment Mar 19, 2026 9:14pm

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