Skip to content

⚡ Bolt: [performance improvement] Array Filtering O(N*M) Set Optmization#380

Draft
yeboster wants to merge 1 commit into
mainfrom
bolt-performance-array-set-optimizations-17356591773687273091
Draft

⚡ Bolt: [performance improvement] Array Filtering O(N*M) Set Optmization#380
yeboster wants to merge 1 commit into
mainfrom
bolt-performance-array-set-optimizations-17356591773687273091

Conversation

@yeboster

Copy link
Copy Markdown
Contributor

💡 What:

  • Replaced Array.prototype.includes checks within filter with Set.prototype.has lookups for large API data structures in voter add and remove functions.
  • Precomputed metaNamesSdk.config.byoc validation mapping into a module-level Set in the domain fees API.

🎯 Why:
Using .includes() inside .filter() introduces an O(N*M) time complexity loop pattern which degrades exponentially with array sizes, specifically when comparing potentially large owners datasets against voters lists. Recalculating static values per endpoint call redundantly wastes compute.

📊 Impact:

  • Reduces filtering complexity from O(N*M) to O(N+M) for voter processing endpoints, speeding up execution significantly for large datasets.
  • Reduces repetitive configuration mapping time per request to O(1) constant lookups in the domains API.

🔬 Measurement:
Run API unit and integration tests to confirm the optimized endpoints function correctly and uniformly relative to their original definitions. Wait times on these endpoints under high load with large datasets will be empirically reduced.


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

Optimized array filtering by replacing O(N) `Array.includes` inside `Array.filter` with an O(1) `Set.has` lookup, reducing filtering complexity from O(N*M) to O(N). Also moved static array mapping in the fees endpoint to a precomputed module-level Set to prevent repeated per-request processing overhead.

Co-authored-by: yeboster <[email protected]>
@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

vercel Bot commented Jun 27, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
app Ready Ready Preview, Comment Jun 27, 2026 8:26pm

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