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: Sun, 26 Nov 2017 23:37:40 -0500 [thread overview]
Message-ID: <20171127043740.GA5994@sigill> (raw)
In-Reply-To: <xmqqo9noe3u0.fsf@gitster.mtv.corp.google.com>
On Mon, Nov 27, 2017 at 01:35:35PM +0900, Junio C Hamano wrote:
> Takuto Ikuta <tikuta@google.com> writes:
>
> > diff --git a/fetch-pack.c b/fetch-pack.c
> > index 008b25d3db087..0184584e80599 100644
> > --- a/fetch-pack.c
> > +++ b/fetch-pack.c
> > @@ -716,7 +716,7 @@ static int everything_local(struct fetch_pack_args *args,
> > for (ref = *refs; ref; ref = ref->next) {
> > struct object *o;
> >
> > - if (!has_object_file(&ref->old_oid))
> > + if (!has_object_file_with_flags(&ref->old_oid, OBJECT_INFO_QUICK))
> > continue;
> >
>
> It appears that great minds think alike?
>
> cf. https://public-inbox.org/git/20171120202920.7ppcwmzkxifywtoj@sigill.intra.peff.net/
It's funny that we'd get two patches so close together. AFAIK the
slowness here has been with us for years, and I just happened to
investigate it recently.
> The 5-patch series that contains the same change as this one is
> cooking and will hopefully be in the released version before the end
> of the year.
I'd be curious if the 5th patch there provides an additional speedup for
Takuto's case.
-Peff
next prev parent reply other threads:[~2017-11-27 4:37 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 [this message]
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
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=20171127043740.GA5994@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.