Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unusually large repo size when running git clone #75

Closed
jakedetels opened this issue Jun 20, 2016 · 5 comments
Closed

Unusually large repo size when running git clone #75

jakedetels opened this issue Jun 20, 2016 · 5 comments

Comments

@jakedetels
Copy link

jakedetels commented Jun 20, 2016

When running git clone https://github.com/components/ember.git, it appears the overall size of the repo is unusually large (1.31 GB) - see screenshot below.

image

I've found that there is one particular hidden file that is very large: ember\.git\objects\pack\pack-8f0fcba433cb69171896f744812f9be0df425d12.pack, which is 1.3 GB. I'm not sure what this file is. One of my colleagues validated that he gets the same results when attempting to clone this repo.

Additionally, prior to cloning this repo, I did a fresh install of git. I have the latest version of git for Windows (see screenshot below). I'm not clear whether this issue is related to: 1) this components/ember repo, 2) github, or 3) this version of git.

image

@alexhancock
Copy link

For what it is worth... I ran a git gc --aggressive on our copy of this repo, and it make the pack file go from 1.6gb to 100mb.

Someone who has control over this repo could do that for this remote copy.

@rwjblue
Copy link
Contributor

rwjblue commented Feb 11, 2017

Not sure how to tell GitHub's servers to run git gc...

@alexhancock
Copy link

So, one thing you can do is just to run...

git gc --aggressive

... on your own machine and then delete the repo and immediately re-create and push.

It's just an issue with the remote hosted by github.

@alexhancock
Copy link

That might create a situation where you'd lose all GitHub specific data (issues/stars and whatnot) though... We didn't have to think about this issue with our internal copy.

It may be a better idea to file a support ticket with GitHub.

@rwjblue
Copy link
Contributor

rwjblue commented Jan 14, 2018

I deleted a few larger branches, I believe that will resolve this...

@rwjblue rwjblue closed this as completed Jan 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants