From: Дилян Палаузов Date: Wed, 18 Mar 2015 14:48:42 GMT Subject: Re: git pull & git gc Message-ID: <5509904A.2000606@aegee.org> In-Reply-To: Hello Duy, #ls .git/objects/17/* | wc -l 30 30 * 256 = 7 680 > 6 700 And now? Do I have to run git gc --aggressive ? Kind regards Dilian On 18.03.2015 15:33, Duy Nguyen wrote: > On Wed, Mar 18, 2015 at 9:23 PM, Дилян Палаузов > wrote: >> Hello, >> >> # git gc --auto >> Auto packing the repository in background for optimum performance. >> See "git help gc" for manual housekeeping. >> >> and calls in the background: >> >> 25618 1 0 32451 884 1 14:20 ? 00:00:00 git gc --auto >> 25639 25618 51 49076 49428 0 14:20 ? 00:00:07 git prune --expire >> 2.weeks.ago >> >> # git count-objects -v >> count: 6039 > > loose number threshold is 6700, unless you tweaked something. But > there's a tweak, we'll come back to this. > >> size: 65464 >> in-pack: 185432 >> packs: 1 > > Pack threshold is 50, You only have one pack, good > > OK back to the "count 6039" above. You have that many loose objects. > But 'git gc' is lazier than 'git count-objects'. It assume a flat > distribution, and only counts the number of objects in .git/objects/17 > directory only, then extrapolate for the total number. > > So can you see how many files you have in this directory > .git/objects/17? That number, multiplied by 256, should be greater > than 6700. If that's the case "git gc" laziness is the problem. If > not, I made some mistake in analyzing this and we'll start again. >