Re: object/pack size x5 larger than a fresh clone?
- From
- Hin-Tak Leung <hintak.leung@gmail.com>
- Date
- Jul 26, 2010, 18:42 UTC
- Message-ID
- <AANLkTimLAROADKgWvEXa9QyyDGbWQGP+9BdbcN4fMHJ0@mail.gmail.com>
- In-Reply-To
- <4C4D42BA.6070900@op5.se>
On 7/26/10, Andreas Ericsson <ae@op5.se> wrote:
Show 35 quoted lines
> On 07/24/2010 11:57 PM, Hin-Tak Leung wrote: >> Is there any reason why a fresh git clone has a object pack around >> 140MB but one that has been updated over the years has it over 700MB? >> (even with git gc --aggressive --prune=now and git fsck?) >> >> $ du .git/objects/ >> 711364 .git/objects/pack >> >> $ du *wine/.git/objects/pack >> 144692 git-wine/.git/objects/pack >> 144604 wine/.git/objects/pack >> >> I had a problem with git fetch "Cannot obtain needed object" from >> wine's git repository (which seems to be something to do with http >> proxy, although AFAIK I don't have one) since about 2 weeks ago which >> obviously does not apply to anybody else as I would have heard from >> wine-devel. >> >> Editing .git/config to switch from a http url to git url cure it... >> but in the course of investigating, I git clone fresh (there are only >> about 3 local changes so I could just git-format-patch them and move >> them) >> >> http://source.winehq.org/git/wine.git >> git://source.winehq.org/git/wine.git >> >> and I am a bit surprised that the new clones are so much smaller than >> the one I have been working on these last few years. (I have had the >> old one for at least 3-4 years). > > To make a fair comparison, try > git repack -a -f -d && git prune --expire=now > > in your old repository. Be warned that this will remove all commits > reachable from reflogs but not from branch heads or tags though.
I have tried as you said, and it has gone slightly worse - $ du .git/objects/ 741172 .git/objects/pack 16 .git/objects/info 741196 .git/objects/
However, I think I found one very big anormaly - in most of my git clones (I have ~20 projects I track) , .git/object/pack consists of pairs of files like this:
pack-<sha1>.idx pack-<sha1>. pack
with the occasional 3rd member, "pack-<sha1>. keep" . I did not look before I did the above, but now the strange repository consists of one such pair to about 147MB, which has a very new time stamp, but a lot of singular pack-<sha1>.idx without a corresponding pack-<sha1>.pack , and some of them quite large, and many of them has time stamps going back to Mar 2008. I have got almost 500 of them, and they vary from about 1.2k to 12MB, so it adds up to over 550MB.
So I guess these *.idx without a corresponding *.pack are safe to delete? But git gc or one of the other house keeping commands should get rid of them though, I think.
Should I file a bug etc for this? Thanks a lot any how.
Hin-Tak