git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Peter Kassak" <cache.sk@gmail.com>, git@vger.kernel.org
Subject: Re: Extremely long subtree split duration
Date: Sat, 09 Nov 2024 15:27:42 +0100	[thread overview]
Message-ID: <447bb623-28be-4667-b571-935ff7d163d0@app.fastmail.com> (raw)
In-Reply-To: <bc028fc5-c0e3-4d31-9790-86bdd3911cc5@app.fastmail.com>

On Fri, Nov 8, 2024, at 23:07, Kristoffer Haugsbakk wrote:
> On Fri, Nov 8, 2024, at 22:40, Peter Kassak wrote:
>> Main difference (except OS) is git version. On Ubuntu is latest
>> installed via apt 2.43.0, on Windows is 2.47.0.windows.2.
>
> I tried a bit on Ubuntu 22.04, Git 2.47.0.  I gave it 14 minutes and then
> it was apparently about 10000/32714 done.
>
> --
> Kristoffer Haugsbakk

I tried again and ran the whole command.  It took 3 hours and 43
minutes.  My `/bin/sh` is dash(1).

I then checked out the first parent of the commit that you pointed to:
bcf524023e (Merge branch 'zf/subtree-split-fix', 2024-02-02).  In other
words I checked out bbc8c05670 (Merge branch 'jc/ls-files-doc-update',
2024-02-02).

A *split* on that took 3m49s.

-- 
Kristoffer Haugsbakk

  reply	other threads:[~2024-11-09 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 21:40 Extremely long subtree split duration Peter Kassak
2024-11-08 22:07 ` Kristoffer Haugsbakk
2024-11-09 14:27   ` Kristoffer Haugsbakk [this message]
2024-11-09 21:10     ` Peter Kassak
2024-11-29 19:44       ` Kristoffer Haugsbakk
2024-11-29 19:50         ` Kristoffer Haugsbakk

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=447bb623-28be-4667-b571-935ff7d163d0@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail.com \
    --cc=cache.sk@gmail.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 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).