git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ronan Pigott" <ronan@rjp.ie>
To: git@vger.kernel.org
Subject: Fetching too many tags?
Date: Thu, 10 Aug 2023 06:08:34 +0000	[thread overview]
Message-ID: <274ec1a2152b0fd53b35c1591f5177e0b0713430@rjp.ie> (raw)

Hey git,

I am interested in git performance today and can't figure out what's going on
here. I was wondering why my git-fetch might be slow in an up-to-date repo:

  $ git pull
  Already up to date.
  $ time git fetch origin master
  From https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux
   * branch                      master     -> FETCH_HEAD
  git fetch origin master  0.13s user 0.06s system 10% cpu 1.705 total

GIT_TRACE_CURL shows it spends most of the time transfering (all) tags from the
remote. It's much faster with --no-tags:

  $ time git fetch -n origin master
  From https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux
   * branch                      master     -> FETCH_HEAD
  git fetch -n origin master  0.11s user 0.03s system 36% cpu 0.383 total

But I don't have tagOpt set:

  $ git config remote.origin.tagOpt || echo $?
  1

And the remote doesn't have to send me any commits, so I don't see why I should
receive any tags at all. Why might I be receiving so many tags?

Thanks,
Ronan

             reply	other threads:[~2023-08-10  6:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  6:08 Ronan Pigott [this message]
2023-08-11 18:09 ` Fetching too many tags? Jeff King
2023-08-11 22:06 ` Ronan Pigott
2023-08-11 23:58   ` Jeff King
2023-08-12  1:04   ` Ronan Pigott

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=274ec1a2152b0fd53b35c1591f5177e0b0713430@rjp.ie \
    --to=ronan@rjp.ie \
    --cc=git@vger.kernel.org \
    /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).