From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Takuto Ikuta <tikuta@google.com>, git@vger.kernel.org
Subject: Re: [PATCH] Use OBJECT_INFO_QUICK to speedup git fetch-pack
Date: Mon, 27 Nov 2017 00:04:20 -0500 [thread overview]
Message-ID: <20171127050420.GB6858@sigill> (raw)
In-Reply-To: <xmqqk1yce301.fsf@gitster.mtv.corp.google.com>
On Mon, Nov 27, 2017 at 01:53:34PM +0900, Junio C Hamano wrote:
> > I'd be curious if the 5th patch there provides an additional speedup for
> > Takuto's case.
>
> Indeed, it is a very good point.
>
> IIUC, the 5th one is about fetching tons of refs that you have never
> seen, right? If a repository that has trouble with everything-local
> is suffering because it right now has 300k remote-tracking branches,
> I'd imagine that these remote-tracking branches are being added at a
> considerable rate, so I'd not be surprised if these "new" refs
> benefits from that patch. And it would be nice to know how much a
> real life scenario actually does improve.
Right, I think it will only kick in for new refs (and maybe deleted
ones, but I didn't check).
I actually did have a real life scenario that was improved, but it's not
very typical. As I've mentioned before, we keep a big shared-object
repository for forks of a single repo, so a fairly common operation is
git -C network.git fetch ../$fork.git +refs/*:refs/remotes/$fork/*
The first time that's run on a fork, everything looks like a new ref.
So "real life", but thankfully not life for most git users. :)
-Peff
prev parent reply other threads:[~2017-11-27 5:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 4:27 [PATCH] Use OBJECT_INFO_QUICK to speedup git fetch-pack Takuto Ikuta
2017-11-27 4:35 ` Junio C Hamano
2017-11-27 4:37 ` Jeff King
2017-11-27 4:53 ` Junio C Hamano
2017-11-27 5:01 ` Takuto Ikuta
2017-11-27 21:24 ` Johannes Schindelin
2017-11-27 23:52 ` Junio C Hamano
2017-11-28 0:33 ` Johannes Schindelin
2017-11-28 1:58 ` Takuto Ikuta
2017-11-28 11:27 ` Johannes Schindelin
2017-11-28 11:35 ` Takuto Ikuta
2017-11-27 5:04 ` Jeff King [this message]
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=20171127050420.GB6858@sigill \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tikuta@google.com \
/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).