Cloned repo is large (433MB)
See original GitHub issue.git/objects/pack (295 MB)
The largest chunk of this is from a large file within .git/objects/pack
(295 MB):
-r--r--r-- 1 dlite staff 295M Feb 6 06:19 pack-0748331a0ae468ca5a9b5bee41418f549ba5da00.pack
git verify-pack -v pack-0748331a0ae468ca5a9b5bee41418f549ba5da00.pack \
> | sort -k 3 -n \
> | tail -10
e15384968d47a2e872030a79ea0cb7dced9f55e6 blob 10699686 1693489 176982870
c25229a9a5baacc4d329b19607f57f68d4f5e1e7 blob 11669167 11239986 156585534
34b3a22cea76771375c88d2759aa397b19e41d72 blob 12001915 1873891 173316462
c228dda8b728160ef64ecfc93a2917105e611734 blob 13721024 12389225 264320842
92aa84d7737c0e7f2f18948efb6366b6fa3115dc blob 14480768 10688751 80481154
a27dd3f3b30dccfa84381d2e78db96ec31854af5 blob 14485504 10693136 100915888
453306b0fd84f7100aebe6faada019cbebddb6bb blob 17373318 2765131 167825520
a0b91c133e07bce25fe5391da0d3a3d7f3a7157e blob 17416012 2760363 151965320
a379aad59c03317f33353a71a866e51d1cfaae2b blob 23778880 21935094 276710132
0f249d5573b25944b99aa9a84176928a1b35f696 blob 42642112 39501577 179054474
These appear to be from the mechanical files which have been removed from the repo:
git rev-list --objects --all | grep e15384968d47a2e872030a79ea0cb7dced9f55e6
e15384968d47a2e872030a79ea0cb7dced9f55e6 Mechanical_Models/BW1099_R3M2E3_KTHSNF.step
Dereks-MacBook-Pro:pack dlite$ git rev-list --objects --all | grep c25229a9a5baacc4d329b19607f57f68d4f5e1e7
c25229a9a5baacc4d329b19607f57f68d4f5e1e7 Mechanical_Models/BW1097_R2M2E2.zip
See this comment from another repo w/a similar issue on how to cleanup this disk space.
nn folder (66 MB)
du -h nn/
52M nn//object_detection_4shave
4.8M nn//object_recognition_4shave/emotion_recognition
9.5M nn//object_recognition_4shave/landmarks
14M nn//object_recognition_4shave
66M nn/
/cc @Luxonis-Brandon
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
git clone issue: repo too large? (50m) - Stack Overflow
I created a fresh new repo, clones just fine. Once I add my site files to it and push them to the remote...
Read more >How to handle big repositories with Git | Atlassian Git Tutorial
Git's shallow clone option allows you to pull down only the latest n commits of the repo's history. How do you do it?...
Read more >Troubleshooting cloning errors - GitHub Docs
If you're having trouble cloning a repository, check these common errors.
Read more >Cleaning up a git repo for reducing the repository size - Medium
Cloning a repository clones the entire history — including every version of every source code file. If a user commits a huge file,...
Read more >Get up to speed with partial clone and shallow clone
If you are working with an extremely large monorepo, then these tradeoffs are more likely to be worthwhile or even necessary to interact ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FIxed. Repo size was reduced by rewriting repo history.
Thanks, Szabi. And thanks @ColbyToland for the advice here. 😃