git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Extremely long subtree split duration

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Nov 9, 2024, 14:27 UTC
Message-ID
<447bb623-28be-4667-b571-935ff7d163d0@app.fastmail.com>
In-Reply-To
<bc028fc5-c0e3-4d31-9790-86bdd3911cc5@app.fastmail.com>
On Fri, Nov 8, 2024, at 23:07, Kristoffer Haugsbakk wrote:
Show 9 quoted lines
> 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
Previous: Kristoffer HaugsbakkNext: Peter Kassak
Message 3 of 6 in “Extremely long subtree split duration”
  1. Peter KassakNov 8, 2024
  2. Kristoffer HaugsbakkNov 8, 2024
  3. Kristoffer HaugsbakkNov 9, 2024
  4. Peter KassakNov 9, 2024
  5. Kristoffer HaugsbakkNov 29, 2024
  6. Kristoffer HaugsbakkNov 29, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.