Activity 2: Analysis #2
Comments
|
Here's my git-sizer output: |
|
@toddocon That looks good in general. The 200MB file might be a good candidate for Git LFS. |
|
Here is my git-sizer output: |
|
My results 😬 git-sizer git-sizer --verbose
Processing blobs: 19360
Processing trees: 34523
Processing commits: 7588
Matching commits to trees: 7588
Processing annotated tags: 0
Processing references: 116
| Name | Value | Level of concern |
| ---------------------------- | --------- | ------------------------------ |
| Overall repository size | | |
| * Commits | | |
| * Count | 7.59 k | |
| * Total size | 3.02 MiB | |
| * Trees | | |
| * Count | 34.5 k | |
| * Total size | 16.5 MiB | |
| * Total tree entries | 444 k | |
| * Blobs | | |
| * Count | 19.4 k | |
| * Total size | 1.88 GiB | |
| * Annotated tags | | |
| * Count | 0 | |
| * References | | |
| * Count | 116 | |
| | | |
| Biggest objects | | |
| * Commits | | |
| * Maximum size [1] | 39.5 KiB | |
| * Maximum parents [2] | 2 | |
| * Trees | | |
| * Maximum entries [3] | 193 | |
| * Blobs | | |
| * Maximum size [4] | 521 MiB | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
| | | |
| History structure | | |
| * Maximum history depth | 3.20 k | |
| * Maximum tag depth | 0 | |
| | | |
| Biggest checkouts | | |
| * Number of directories [5] | 218 | |
| * Maximum path depth [6] | 10 | * |
| * Maximum path length [7] | 138 B | * |
| * Number of files [5] | 1.26 k | |
| * Total size of files [8] | 813 MiB | |
| * Number of symlinks [9] | 1 | |
| * Number of submodules | 0 | |git-find-lfs-extensions /Users/brentconn/IdeaProjects/grafting-monorepos/scripts/git-find-lfs-extensions
Type Extension LShare LCount Count Size Min Max
------- --------- ------- ------- ------- ------- ------- -------
all * 1.0 % 17 1141 144 0 105
binary bson 16.0 % 2 12 107 0 105
binary gz 10.0 % 4 39 7 0 2
binary png 3.0 % 5 146 18 0 0
text json 3.0 % 4 101 4 0 1
text js 0.0 % 1 553 3 0 1
text svg 12.0 % 1 8 1 0 0Can't post much else due to sensitive information :) |
|
Extensions: |
|
@alubchuk your repo looks really good. Again the 20MB file might be a good candidate for LFS. In general I recommend to use LFS for files >1MB which are changed regularly. |
|
@onetrickwolf 521 MB files is definitely a candidate for LFS. |
|
@toddocon You have a lot of compiled libraries like |
|
@toddocon I don't know what |
|
What of these results files are of the most interest? |
|
The first 3 lines of each of those could be interesting: |
|
Example from directories-deleted-sizes.txt: Example from directories-all-sizes.txt: |
|
@toddocon These apps are just present in the history. They are not in the HEAD commit but you carry around the data with every clone. In the next section we will discuss what you can do about it 😉
|
|
the final ones: |
@toddocon ☝️ |
|
git-sizer Processing blobs: 2222
|
|
@thomas-schuster your repo looks perfect! |
|
Processing blobs: 4388
|
|
Please any comments and suggestion about the result from “git-sizer --verbose” for my work repository？ |
|
@neilwang0913 In general your repository is in great shape and there is no reason for concern. The single 58 MB file might be a good candidate for Git LFS, but since your overall repository size is rather low that is no big concern. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Duration: 20 minutes
We will use different analysis tools to identify wrong practices in a repository. To do it we will use the following commands:
Before starting any analysis, pick one repository of your preference that you would like to analyze.
Clone this repository as we have added all the tools into the it for making the workshop more convenient:
Stats of repo size:
git-sizergit-sizer.Find files that should be in LFS:
git-find-lfs-extensionsgrafting-monoreposrepositoryPrint directories with the number of files contained:
git-find-dirs-many-filesgrafting-monoreposrepositoryFind dirs that should not be committed:
git-find-dirs-unwantedgrafting-monoreposrepository/path/to/grafting-monorepos/scripts/git-find-dirs-unwanted | head -n 15Analyze the repository:
git-filter-repo --analyzegit-filter-repotoolReport out
Report your findings from the above commands in comments section below. Be sure to include answers to the following questions in your comments, if possible:
- Do you find any patterns?
- Was there anything surprising?
For examples and more information, please see README.md -> Activity 2.
The text was updated successfully, but these errors were encountered: