[DecisionNerd]

Summary

Implements #512: parallel preferential_attachment on ComputePool with measured crossover and fingerprint parity.

Closes #512

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Note

Parallelize preferential_attachment scoring on ComputePool above 262,144 work units

• Adds a parallel execution path for preferential_attachment_scores in algorithm_rank.rs that partitions sources into canonical chunks and processes them concurrently on the instance-owned ComputePool.
• Introduces select_preferential_attachment_path to choose serial vs. parallel based on thread count, pool availability, source count, and estimated work (sources + total neighbor count).
• Serial path remains the default when threads ≤ 1, sources ≤ 1, estimated work < 262,144, or no pool is available; score values and row order are identical on both paths.
• Worker panics during parallel execution are caught and returned as structured ExecutionError rather than unwinding past the pool boundary.
• Behavioral Change: graphs with estimated work ≥ 262,144 and multiple configured threads now execute preferential attachment in parallel by default.

^{Macroscope summarized 328871e.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 48 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 60df305b-0797-45ac-8e03-db973f5e7f83

📥 Commits

Reviewing files that changed from the base of the PR and between 1acf5b0 and 328871e.

⛔ Files ignored due to path filters (2)

• docs/book/architecture/algorithms.md is excluded by !**/*.md, !**/docs/**
• docs/reference/api.md is excluded by !**/*.md, !**/docs/**

📒 Files selected for processing (2)

• crates/graphforge-api/tests/m4_entry_baseline.rs
• crates/graphforge-exec/src/algorithm_rank.rs

---

_{Comment @coderabbitai help to get the list of available commands.}