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, 12 Oct 2021 17:39:25 -0400 [thread overview]
Message-ID: <YWYAjRfLsDtc1Dkm@coredump.intra.peff.net> (raw)
In-Reply-To: <d8abab7fb5184a94a9e9e5b7c1f28695@xiaomi.com>
On Tue, Oct 12, 2021 at 09:08:08AM +0000, 程洋 wrote:
> Jesus. It works for me. After disable writebitmap, time cost decrease
> from 33 seconds to 0.9 seconds.
>
> But now it turns out that, remote side takes 13 seconds to receive the
> pack, since git receive-pack is triggered automatically from remote
> side, is there anyway to enable GIT_TRACE2_PERF on server side?
For the environment variable, it depends on your protocol. If you can
push over ssh (and the other side lets you execute arbitrary commands),
then:
git push --receive-pack='GIT_TRACE2_PERF=/tmp/foo.trace git-receive-pack'
Otherwise, you can look at setting the trace2.perfTarget config option
on the server side. I haven't played with it myself before.
-Peff
next prev parent reply other threads:[~2021-10-12 21:39 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 [this message]
2021-10-14 6:47 ` 程洋
2021-10-26 21:54 ` Jeff King
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
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=YWYAjRfLsDtc1Dkm@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.
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).