Skip to content

⚡ Bolt: Fast spatial checks for auto_k_selection and DBSCAN#144

Open
teerthsharma wants to merge 1 commit into
masterfrom
bolt-clustering-spatial-opt-16304022299482913376
Open

⚡ Bolt: Fast spatial checks for auto_k_selection and DBSCAN#144
teerthsharma wants to merge 1 commit into
masterfrom
bolt-clustering-spatial-opt-16304022299482913376

Conversation

@teerthsharma

Copy link
Copy Markdown
Owner

💡 What: Optimized spatial neighborhood queries in auto_k_selection and DBSCAN::region_query within ml::clustering.rs.
🎯 Why: Previously, these algorithms calculated Euclidean distances by calling distance(), which internally uses libm::sqrt. In spatial loops performing $O(N^2)$ checks, taking the square root for every pair is a known major performance bottleneck.
📊 Impact: By calculating the squared epsilon threshold (eps_sq) upfront and breaking early inside the dimension loop if the accumulated squared sum exceeds it (!(sum < eps_sq)), we completely eliminate the square root and reduce the number of dimension iterations, yielding significantly faster clustering bounds.
🔬 Measurement: Confirmed clustering logic remains correct as all topological and clustering tests (cargo test -p aether-core) pass identically.


PR created automatically by Jules for task 16304022299482913376 started by @teerthsharma

Replaced `distance()` (which uses `libm::sqrt`) with inline squared distance
calculations (`sum < eps_sq`) in `auto_k_selection` and `DBSCAN::region_query`.
This avoids the expensive square root operation in the hot inner loops of these
spatial algorithms. Added NaN-safe comparisons `!(sum < eps_sq)` for robust handling.

Co-authored-by: teerthsharma <78080953+teerthsharma@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