From: Jeff King <peff@peff.net>
To: 程洋 <chengyang@xiaomi.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [External Mail]Re: why git is so slow for a tiny git push?
Date: Tue, 26 Oct 2021 17:54:30 -0400 [thread overview]
Message-ID: <YXh5FoeyfePqr1k3@coredump.intra.peff.net> (raw)
In-Reply-To: <5063751fd4b94ccca3987080c96370d8@xiaomi.com>
On Thu, Oct 14, 2021 at 06:47:31AM +0000, 程洋 wrote:
> Seems that git receive-pack only takes 1 seconds.
> After that, git rev-list takes the most time, I don't know what is it doing
It's checking connectivity of what was sent (i.e., that the other side
sent us all the objects). If you have a ton of refs on the server side,
there are some known issues here, as just loading the "we already have
this" side of the traversal can be very expensive.
There's been some recent work to make this faster, like f559d6d45e
(revision: avoid hitting packfiles when commits are in commit-graph,
2021-08-09) and f45022dc2f (connected: do not sort input revisions,
2021-08-09), which will be in the upcoming release. I'm sure there are
more improvements that could be made on top, but those show the general
direction.
-Peff
next prev parent reply other threads:[~2021-10-26 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c5a8595658d6416684c2bbd317494c49@xiaomi.com>
[not found] ` <5a6f3e8f29f74c93bf3af5da636df973@xiaomi.com>
2021-10-09 18:05 ` why git is so slow for a tiny git push? 程洋
2021-10-11 16:53 ` Jeff King
2021-10-12 8:04 ` [External Mail]Re: " 程洋
2021-10-12 8:39 ` Jeff King
2021-10-12 9:08 ` 程洋
2021-10-12 21:39 ` Jeff King
2021-10-14 6:47 ` 程洋
2021-10-26 21:54 ` Jeff King [this message]
2021-10-27 2:48 ` 程洋
2021-10-12 10:06 ` Ævar Arnfjörð Bjarmason
2021-10-12 21:46 ` Jeff King
2021-11-23 6:42 ` 程洋
2021-11-24 18:15 ` Jeff King
2021-11-25 2:53 ` 程洋
2021-11-24 8:07 ` 程洋
2021-10-28 13:17 ` Han-Wen Nienhuys
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=YXh5FoeyfePqr1k3@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chengyang@xiaomi.com \
--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 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.