Re: Git 2.26 fetches many times more objects than it should, wasting gigabytes

[Jeff King <peff@peff.net>]

On Wed, Apr 22, 2020 at 08:40:25AM -0700, Jonathan Nieder wrote:

> I think this still suggests that we should go ahead and switch
> negotiation algorithms, both because it avoids this MAX_IN_VAIN and
> because it reduces the number of rounds needed to make progress.

I'd be happier about that if the other algorithm turned up the same pack
that v0 does. But it has twice as many objects.

It looks to me like v0 is just more aggressive about digging in the
history. That _does_ cost more rounds, but this example shows that
there's a benefit to doing so for real-world cases.

> I'd also be tempted to get rid of MAX_IN_VAIN.  If we're at the point
> of giving up, shouldn't we error out instead of having the server send
> a copy of the entirety of history?

How would you fetch in cases where the client and server legitimately
don't have any common commits?

You could add a flag to force it, but I don't know that you're really
making users any happier. Fetching the whole history is annoying, but
refusing to fetch at all is perhaps more so. From the user's perspective
either the full fetch is what they want, or Git is broken.

-Peff