git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Tan <jonathantanmy@google.com>,
	git@vger.kernel.org, Jeff King <peff@peff.net>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Fetching 24 Linux commits = 1.2 GiB
Date: Wed, 15 Apr 2020 11:52:30 -0700	[thread overview]
Message-ID: <20200415185230.GA216285@google.com> (raw)
In-Reply-To: <xmqq1roo947y.fsf@gitster.c.googlers.com>

Hi,

>> On Wed, Apr 15, 2020 at 10:01:46AM +0200, Jiri Slaby wrote:

>>> I was at 8f3d9f354286 of:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>>
>>> I did git remote update today and it fetched:
>>> Receiving objects: 100% (7330823/7330823), 1.20 GiB
>>> It updated master: 8f3d9f354286..8632e9b5645b, that is 24 small commits.

I suspect this is due to negotiation differing in protocol v2: in
protocols that do not maintain server side state, we have to record
previously matched "have"s at each round and the number of additional
"have"s sent on top leads the server to have insufficient information
about what the client has.  In other words, I suspect that with
https:// in protocol v0 you would experience the same thing.

Does

	git config --global fetch.negotiationStrategy skipping

help?

Thanks,
Jonathan

  parent reply	other threads:[~2020-04-15 19:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15  8:01 Fetching 24 Linux commits = 1.2 GiB Jiri Slaby
2020-04-15  8:11 ` Andreas Schwab
2020-04-15  8:16   ` Jiri Slaby
2020-04-15  8:23     ` Andreas Schwab
2020-04-15  8:27       ` Jiri Slaby
2020-04-15  8:34         ` Andreas Schwab
2020-04-15 10:52 ` Kevin Daudt
2020-04-15 13:56 ` Konstantin Ryabitsev
2020-04-15 15:08   ` Junio C Hamano
2020-04-15 15:16     ` Jeff King
2020-04-15 18:52     ` Jonathan Nieder [this message]
2020-05-20  8:53     ` Andreas Schwab
2020-05-20  8:57       ` Andreas Schwab
2020-05-20 10:05       ` Michal Suchánek
2020-05-20 10:34         ` Andreas Schwab
2020-05-20 19:40       ` Jeff King
2020-05-25 18:22         ` Lukas Wunner
2020-05-25 18:37           ` Junio C Hamano
2020-04-16  6:31   ` Jiri Slaby
2020-04-21 10:02     ` Martin Wilck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200415185230.GA216285@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonathantanmy@google.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).