Skip to content

⚡ Bolt: Optimize is_neighbor check with squared distance#136

Open
teerthsharma wants to merge 1 commit into
masterfrom
bolt-is-neighbor-opt-762965749435470350
Open

⚡ Bolt: Optimize is_neighbor check with squared distance#136
teerthsharma wants to merge 1 commit into
masterfrom
bolt-is-neighbor-opt-762965749435470350

Conversation

@teerthsharma

Copy link
Copy Markdown
Owner

💡 What: Optimized ManifoldPoint::is_neighbor in aether-core to use a squared distance comparison and early-exit loop instead of calling the full Euclidean .distance() method which involves libm::sqrt.

🎯 Why: The is_neighbor check is invoked constantly during spatial scanning (such as $O(N)$ searches in SparseAttentionGraph::add_point). The mathematical constraint $d < \epsilon$ is strictly equivalent to $d^2 < \epsilon^2$ for $\epsilon > 0$. By comparing the squared distance, we completely avoid the very expensive square root calculation. Furthermore, since the distance squared incrementally accumulates over each coordinate, we can early-exit if the sum exceeds $\epsilon^2$ at any point.

📊 Impact: This removes a major mathematical bottleneck for point cloud additions and spatial querying, reducing CPU overhead inside hot loops and improving overall throughput.

🔬 Measurement: Verify by running cargo test -p aether-core manifold to confirm that spatial logic remains intact. Micro-benchmarking the spatial addition graphs will show notable gains as point counts rise.


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

Replaced Euclidean distance comparison requiring libm::sqrt with a squared
distance comparison. This adds early exit capabilities and rejects NaN/negative
thresholds early, boosting performance in high-frequency spatial loops like
SparseAttentionGraph::add_point.

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