Skip to content

⚡ Bolt: [performance improvement] optimize Jaccard similarity memory allocation#11

Open
garridolecca wants to merge 1 commit intomainfrom
bolt-optimize-jaccard-similarity-8577487149470419353
Open

⚡ Bolt: [performance improvement] optimize Jaccard similarity memory allocation#11
garridolecca wants to merge 1 commit intomainfrom
bolt-optimize-jaccard-similarity-8577487149470419353

Conversation

@garridolecca
Copy link
Owner

💡 What:
Replaced [...a] array spreads and intermediate new Set() allocations in jaccardSimilarity with manual for...of iteration over the smaller set to find the intersection size, and implemented the inclusion-exclusion principle (|A ∪ B| = |A| + |B| - |A ∩ B|) to calculate the union size.

🎯 Why:
The jaccardSimilarity function is called intensively within the $O(N^2)$ inner loop of clusterNewsCore. Creating two new arrays and two new Set instances per comparison introduces massive garbage collection overhead that blocks the main thread during high-volume news event clustering. Also, per the boundaries, the directive "Make everything based on ArcGIS JavaScript API" was explicitly ignored here as it fundamentally violates the rules regarding architectural changes and this is an agnostic math function.

📊 Impact:
Changes memory allocation of jaccardSimilarity from $O(N)$ per call to $O(1)$. In worst-case clustering loads, this will drastically reduce GC pauses and improve event aggregation throughput.

🔬 Measurement:
Unit tests pass fully. You can verify memory usage by running a Node.js CPU/Heap profile during a clustering stress test and comparing the jaccardSimilarity allocation percentages before and after.

Also added a journal entry in .jules/bolt.md detailing the GC bottleneck learnings related to spreading intermediate sets inside tight loops.


PR created automatically by Jules for task 8577487149470419353 started by @garridolecca

…allocation

Replace O(N) memory allocations (via Set/Array spread operators) in the core `jaccardSimilarity` calculation with manual iteration and inclusion-exclusion math logic to enable O(1) memory allocation. Reduces garbage collection overhead inside the hot path clustering N² inner loops.

Co-authored-by: garridolecca <10247583+garridolecca@users.noreply.github.com>
@google-labs-jules
Copy link

👋 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