[DecisionNerd]

Summary

Implements #500: parallel ArticleRank destination-owned updates on the instance-owned ComputePool with measured crossover and bit-identical fingerprints.

Closes #500

  

---

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

Note

Parallelize ArticleRank execution on the instance-owned compute pool

• Adds a destination-owned pull accumulation path for ArticleRank using a prebuilt inbound CSR, replacing the previous push-based source iteration.
• Selects the parallel path when compute_threads > 1, a compute pool is present, and the graph has ≥131,072 edges; otherwise falls back to serial.
• Serial path checkpoints every 4,096 destinations (previously every 1,024 edges); parallel path uses a shared AtomicUsize for periodic cancellation checks.
• Worker panics in the parallel path are caught via catch_unwind and surfaced as a structured AlgorithmError with a stable message.
• Behavioral Change: serial cancellation checkpoint cadence changes from edge-count-based (1,024 edges) to destination-count-based (4,096 destinations).

^{Macroscope summarized b399e4a.}

[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: 7 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: b0e2a8a6-28e2-41e5-a93c-9eaeb6b6fade

📥 Commits

Reviewing files that changed from the base of the PR and between 968e4ed and a33df61.

⛔ Files ignored due to path filters (3)

• docs/book/architecture/algorithms.md is excluded by !**/*.md, !**/docs/**
• docs/development/execution-resource-policy.md is excluded by !**/*.md, !**/docs/**
• docs/reference/api.md is excluded by !**/*.md, !**/docs/**

📒 Files selected for processing (3)

• crates/graphforge-exec/src/algorithm_dispatch.rs
• crates/graphforge-exec/src/algorithm_rank.rs
• crates/graphforge-exec/src/compute_pool.rs

---

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