From: Derrick Stolee <stolee@gmail.com>
To: Tao Klerks <tao@klerks.biz>
Cc: git@vger.kernel.org
Subject: Re: Partial Clone, and a strange slow rev-list call on fetch
Date: Fri, 4 Jun 2021 09:21:49 -0400 [thread overview]
Message-ID: <5ce5286c-9390-7cb5-a039-8e26be990b8d@gmail.com> (raw)
In-Reply-To: <CAPMMpogSepMk07HVtwO8qKaHx2SHmYVB+vnrnWwVWBNo8U5hAQ@mail.gmail.com>
On 6/3/2021 5:10 PM, Tao Klerks wrote:
> On Wed, Jun 2, 2021 at 1:18 PM Derrick Stolee <stolee@gmail.com> wrote:
>
>> could you re-run the scenario with GIT_TRACE2_PERF=1 which will
>> give the full Git process stack as we reach that rev-list call.
>
> Sorry about the delay, I've been trying to reproduce... reproduceably :)
>
> I now have a whole file of examples and observations, attached (I
> assume text attachments are allowed on this mailing list?), which
> should be reproducible for anyone as I was able to use the linux
> kernel repo to illustrate all cases.
I appreciate that you took so much time to investigate here. You
have convinced me that there are deeper things going on than just
the "unshallow, but with filters this time" situation.
I have created an internal issue for my team to investigate this
when we have capacity for it. I don't think it will happen this
month, so if anyone else has the time now then don't wait for us.
Thanks,
-Stolee
next prev parent reply other threads:[~2021-06-04 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 4:56 Partial Clone, and a strange slow rev-list call on fetch Tao Klerks
2021-06-02 11:18 ` Derrick Stolee
2021-06-03 21:10 ` Tao Klerks
2021-06-04 13:21 ` Derrick Stolee [this message]
2021-06-05 6:35 ` Tao Klerks
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=5ce5286c-9390-7cb5-a039-8e26be990b8d@gmail.com \
--to=stolee@gmail.com \
--cc=git@vger.kernel.org \
--cc=tao@klerks.biz \
/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 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 NNTP newsgroup(s).