Re: git-reflog 70 minutes at 100% cpu and counting

From: Nicolas Pitre <nico@fluxnic.net>
Date: Dec 15, 2009, 03:44 UTC
Message-ID: <alpine.LFD.2.00.0912142228121.23173@xanadu.home>
In-Reply-To: <1260843111.9379.86.camel@localhost>

On Mon, 14 Dec 2009, Eric Paris wrote:

Show 14 quoted lines

> On Mon, 2009-12-14 at 19:26 -0500, Nicolas Pitre wrote:
> > On Mon, 14 Dec 2009, Eric Paris wrote:
> > 
> > > Maybe having a .git directory that large is the problem?
> > 
> > Shouldn't be, unless your repo is really badly packed.
> > 
> > What's the output of 'git count-objects -v' ?
> 
> count: 87065
> size: 866744
> in-pack: 1203497
> packs: 148
> size-pack: 976474

So basically 87K loose objects occupying 846 MB and 1.2M packed objects occupying 954 MB across 148 packs. That's an horrible repository layout which would definitely gain by being repacked.

> I noticed just blindly poking at sizes in my .git/object/pack that the
> largest pack is a lot larger than the second and third largest....

That's expected.

> And all total there is almost 1G of data in .git/object/pack
> 
> If the answer really is that I just have too much data and it can't be
> handled,

Nope. git should handle that kind of data set perfectly fine. And once repacked, you should end up with a single pack containing everything and the total size of your .git/objects directory will probably shrink by 50% or more.

But to be able to repack, your 'git reflog' needs to work correctly, and the problem is unlikely to be related to the repository size.

Nicolas