docs: add always-on performance pass to the PR review guide#4040
docs: add always-on performance pass to the PR review guide#4040matt-aitken wants to merge 1 commit into
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🔇 Additional comments (2)
Walkthrough
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Adds a dedicated, always-on Performance section to the repo PR review guide (
.claude/REVIEW.md), so every review weighs new work against table size, hot paths, and how deep or wide the data it walks can get.It names the tables to treat as huge (the
TaskRunfamily in Postgres,task_events_v1/v2in ClickHouse), the hot paths that warrant extra scrutiny (trigger and batch trigger, dequeue, execution-snapshot writes, OTEL ingestion, trace and run-list reads), the deep and wide shapes that turn one run into a large tree or batch, and five named anti-patterns with severities: per-level re-scans, dropping the partition-pruning predicate, unboundedINlists, sequential per-level round-trips, and losing the single-query fast path.