Conversation
get_excluded_paths() checked each walked entry against the accumulated exclude list, so the cost grew with the number of already excluded paths. On a 533k file tree this dominated the call at 111s; a parallel set brings it to 9s with identical return values.
|
FL Source 속도 개선 이슈로 수정하는 건 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe exclusion scan now keeps the existing list for returned paths and adds a set for parent-path checks. A ChangesExclusion lookup optimization
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized performance improvement is merge-ready after normal checks and review; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 2📝 Generate docstrings 💡
🛠️ Fix failing CI checks 💡
🧪 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 |
get_excluded_paths() checked each walked entry against the accumulated exclude list, so the cost grew with the number of already excluded paths. On a 533k file tree this dominated the call at 111s; a parallel set brings it to 9s with identical return values.
Summary by CodeRabbit