feat(cli): source tree histogram through filesystem scans #3195
Conversation
This file contains 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
…hon-fun # Conflicts: # snapshot/snapshotfs/scanner.go
MinyiZou
changed the title
Shrekster
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While investigating some Kopia bugs, we discovered that Kopia lacked a scanning feature for the source tree. During any performance/scale issue, we remain unaware of the filesystem geography. Tools like "tree"/"du" are either too verbose, not fast enough or just do not output all the information needed most of the time. This makes it difficult to estimate the workload, traversal patterns and potentially making it difficult to understand why a snapshot is sluggish. To address this issue, I developed a tool that allows us to preview file conditions and enabling us to make informed and rational choices.