perf: optimize file tree scanning for large repositories #6505
+280
−114
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Karavil
force-pushed
the
perf/file-tree-scanning
branch
4 times, most recently
from
577ff4a to
493a899
Compare
On large repos (42k+ files), file tree generation was taking 8+ seconds because ripgrep scanned ALL files before limiting output. Changes: - Add FileTree module using git ls-files (~7000x faster) - Cache file tree at Instance level - Remove Ripgrep.tree (replaced by FileTree.tree) - Update debug commands to use FileTree Performance (M3 MacBook Pro, 42k file repo): - File tree: 8.39s → ~1ms 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Karavil
force-pushed
the
perf/file-tree-scanning
branch
from
493a899 to
2bfa7ae
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Use
git ls-filesinstead of ripgrep for file tree generation (~7000x faster on large repos).Problem
On large repos (42k+ files), file tree generation was taking 8+ seconds because ripgrep scanned ALL files before limiting output to 200.
Changes
FileTreemodule usinggit ls-files --cached --others --exclude-standardRipgrep.tree(replaced byFileTree.tree)Performance (M3 MacBook Pro, 42k file repo)
🤖 Generated with Claude Code