perf(ui): cap initial file-tree fetch at depth 8 on dashboard#119
Merged
Conversation
Dashboard.tsx called `api.getFileTree()` with no depth, so the backend returned the full tree (capped only by the 10 K maxFiles limit). On a 200 K-node graph that's ~2-4 MB of JSON shipped to the browser on every cold load, even though ECharts treemap only renders one level at a time and drilling is client-side. Cap initial fetch at depth 8 — enough for a fully-qualified Java path (`src/main/java/io/github/<org>/<pkg>/<sub>/File.java` = 8 segments) and the typical TS/Python/Go layouts. Past depth 8 the directory renders as a leaf with its aggregate node count; on-demand subtree fetching for deeper drilling is a follow-up if real workloads need it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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
`Dashboard.tsx` called `api.getFileTree()` with no depth argument, so
the backend returned the full tree (capped only by the 10 K `maxFiles`
limit). On a 200 K-node graph that's ~2-4 MB of JSON shipped to the
browser on every cold load, even though ECharts treemap only renders
one level at a time and drilling is client-side.
Cap the initial fetch at depth 8 — enough for a fully-qualified Java
path (`src/main/java/io/github////File.java` = 8
segments) and the typical TS/Python/Go layouts. Past depth 8 the
directory renders as a leaf with its aggregate node count; on-demand
subtree fetching for deeper drilling is a follow-up if real workloads
need it.
Test plan
🤖 Generated with Claude Code