{"id":2008,"date":"2014-10-14T11:12:02","date_gmt":"2014-10-14T11:12:02","guid":{"rendered":"http:\/\/blog.designed79.co.uk\/?p=2008"},"modified":"2014-10-14T11:12:02","modified_gmt":"2014-10-14T11:12:02","slug":"clean-up-you-git-repo","status":"publish","type":"post","link":"https:\/\/blog.designed79.co.uk\/?p=2008","title":{"rendered":"Clean up you Git Repo"},"content":{"rendered":"

Doing the “git gc” reduced my git repo from 17 GB to 787 MB !!!<\/p>\n

Generally, doing incremental “git gc” is the right approach, and better
\nthan doing “git gc –aggressive”. It’s going to re-use old deltas, and
\nwhen those old deltas can’t be found (the reason for doing incremental GC
\nin the first place!) it’s going to create new ones.<\/p>\n

On the other hand, it’s definitely true that an “initial import of a long
\nand involved history” is a point where it can be worth spending a lot of
\ntime finding the *really*good* deltas. Then, every user ever after (as
\nlong as they don’t use “git gc –aggressive” to undo it!) will get the
\nadvantage of that one-time event. So especially for big projects with a
\nlong history, it’s probably worth doing some extra work, telling the delta
\nfinding code to go wild.<\/p>\n

So the equivalent of “git gc –aggressive” – but done *properly* – is to
\ndo (overnight) something like<\/p>\n

git repack -a -d –depth=250 –window=250<\/p>\n

where that depth thing is just about how deep the delta chains can be
\n(make them longer for old history – it’s worth the space overhead), and
\nthe window thing is about how big an object window we want each delta
\ncandidate to scan.<\/p>\n

And here, you might well want to add the “-f” flag (which is the “drop all
\nold deltas”, since you now are actually trying to make sure that this one
\nactually finds good candidates.<\/p>\n

And then it’s going to take forever and a day (ie a “do it overnight”
\nthing). But the end result is that everybody downstream from that
\nrepository will get much better packs, without having to spend any effort
\non it themselves.<\/p>\n

Linus<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

Doing the “git gc” reduced my git repo from 17 GB to 787 MB !!! Generally, doing incremental “git gc” is the […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2008","post","type-post","status-publish","format-standard","hentry","category-info-on-tech"],"_links":{"self":[{"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2008","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2008"}],"version-history":[{"count":0,"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2008\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2008"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2008"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.designed79.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2008"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}