git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: git@vger.kernel.org, git@vger.kernel.org
Subject: git doing large refetches
Date: Thu, 25 Jun 2020 17:46:05 +0000 (UTC)	[thread overview]
Message-ID: <1731755010.6694064.1593107165458@mail.yahoo.com> (raw)
In-Reply-To: 1731755010.6694064.1593107165458.ref@mail.yahoo.com

Hi,

Lately I noticed that git occasionally do very large re-fetches, despite the difference between local and remote being not large. For example, here are two aborted fetches (see how small the emumerating / counting /compressing are, compared to the receiving object number):

$ git fetch torvalds
remote: Enumerating objects: 19374, done.
remote: Counting objects: 100% (19374/19374), done.
remote: Compressing objects: 100% (4016/4016), done.
^Cceiving objects:   2% (161673/7478285), 80.54 MiB | 2.78 MiB/s

$ git fetch sound
remote: Enumerating objects: 52009, done.
remote: Counting objects: 100% (52009/52009), done.
remote: Compressing objects: 100% (5480/5480), done.
^Cceiving objects:   1% (74819/7481898), 37.92 MiB | 1.98 MiB/s

I don't see any real pattern, as the last few times I fetch from either of those two are also quite small ( a few days ago).

$ git --version
git version 2.26.2

stanzas from my .git/config

[remote "torvalds"]
	url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
	fetch = +refs/heads/*:refs/remotes/torvalds/*
[remote "sound"]
	url = git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
	fetch = +refs/heads/*:refs/remotes/sound/*

Another general issue is that, I used to have just a few small files under .git/objects/XX, with a few large ones under .git/objects/pack . But at the moment, ".git/objects/pack" is 4.4GB, while ".git/objects/" is 5.2GB .


Also, is there a "best practice" if I like to track multiple upstreams (and the convenience of it), while keeping the local repo / heads (the part that "I do", and requiring back-up, etc). I thought of splitting the two into a "mine" repo with "info/alternates" pointing to a pure-fetch-reference-upstream repo; but I am a bit worried about doing a fetch on "mine" before or without updating the "pure-fetch-reference-upstream" repo, in which case I would end up with duplicate objects ending up in mine, and also, would be vulnerable to upstream doing rebase, for example. Any thoughts?

       reply	other threads:[~2020-06-25 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1731755010.6694064.1593107165458.ref@mail.yahoo.com>
2020-06-25 17:46 ` Hin-Tak Leung [this message]
2020-06-25 17:54   ` git doing large refetches Pratyush Yadav
     [not found] <1406746652.7528852.1593187534410.ref@mail.yahoo.com>
2020-06-26 16:05 ` Hin-Tak Leung

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=1731755010.6694064.1593107165458@mail.yahoo.com \
    --to=htl10@users.sourceforge.net \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).