Re: gc getting called on each git command ... what's wrong?

On Wed, 15 Jun 2011, Geoff Russell wrote:

On Thu, Jun 9, 2011 at 2:39 AM, Jakub Narebski [off-list ref] wrote:

quoted

Peter Harris [off-list ref] writes:

quoted

On Tue, Jun 7, 2011 at 9:33 PM, Geoff Russell wrote:

quoted

As of today, almost every time I do a git command, gc is getting
invoked.

quoted

  There are 96 pack files.

That's why. See gc.autopacklimit in "git help config" -- by default,
git will gc if there are more than 50 pack files.

Actually it looks like it is combination of this and packSizeLimit set
to 30M.  Git notices that it has too many packfiles, and tries to
repack them, but packlimit forces Git to split it into small
packfiles... and end up with more packfiles than limit anyway.

Thanks to everybody. This is exactly what was happening and the problems
went away when I set the packSizeLimit higher ... 3000M

 
Why did you set packSizeLimit at all?

 

quoted

Perhaps git should notice that it has nonsensical combination of
options...

That would be nice. It should be reasonably easy to work out that the
packSizeLimit will guarantee too many pack files after the gc.
Disobeying a users wishes shouldn't be undertaken lightly, but sometimes
we stuff up :) 

Well, git can simply notice that each except perhaps on file has
size greater or equal to gc.packSizeLimit, and then ignore gc.autopacklimit
hint, because repacking would not reduce number of packs, and not lower
it below gc.autopacklimit.

If `git gc` is called interactively, we can warn user about this situation...

-- 
Jakub Narebski
Poland

2011/6/16 Jakub Narebski [off-list ref]

Why did you set packSizeLimit at all?

Some time ago (31/8/2010) I had a problem which seemed to be caused by
large packs (>4GB), you
can find it in the git list with a subject of "Large pack causes git
clone failures ... what to do?"

Anyway, I set packSizeLimit and fiddled around for a bit ...
eventually the problem went
away when I moved the central repository to another machine with less load and
more memory. At which point I gave a sigh of relief and forgot to
remove the packSizeLimit
until recently bitten. But the original problem was probably nothing
to do with large
packs and hasn't recurred.

Cheers,
Geoff.

On Thu, 16 Jun 2011, Geoff Russell wrote:

2011/6/16 Jakub Narebski [off-list ref]

quoted

Why did you set packSizeLimit at all?

Some time ago (31/8/2010) I had a problem which seemed to be caused by
large packs (>4GB), you can find it in the git list with a subject of
"Large pack causes git clone failures ... what to do?"

So why did you set packSizeLimit to such ridiculous low value, instead
of 2g (2 GB) or something?

-- 
Jakub Narebski
Poland