Large ".pack" file in repo causes very long clone time
See original GitHub issueHey,
While cloning the repo locally (over SSH) I noticed an unusually long clone time (~5min, 25MB). I tracked this down to this file stored in the git history:
.git/objects/pack/pack-0458eb2f12bd2dd2025bf18c69e7c95a24e8c1c3.pack
I suppose this may be from a previously large object stored in the repo, but not sure. Any idea?
This is not critical at all — just reporting because it could be a bit cumbersome for newcomers. 😃
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to handle big repositories with Git | Atlassian Git Tutorial
The first solution to a fast clone and saving developer's and system's time and disk space is to copy only recent revisions. Git's...
Read more >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 Git Partial Clone lets you fetch only the large file you need
Partial Clone is a new feature of Git that replaces Git LFS and makes working with very large repositories better by teaching Git...
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 >Reducing the size of a git repository with git-replace
If you have you should know it takes a looooong time to clone. ... I don't generally deal with repos that big, but...
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 FreeTop 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
Top GitHub Comments
Deleted the
requests3
branch, which is the only place the large images were included.Appears resolved to me now (based on cloning times before and after the delete).
Seems to be about images in
/docs
…How to remove those files form the history: https://stackoverflow.com/questions/2100907/how-to-remove-delete-a-large-file-from-commit-history-in-git-repository