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

Re: git hangs with --separate-git-dir

From
EEErik Cervin Edin <erik@cervined.in>
Date
May 17, 2023, 07:11 UTC
Message-ID
<CA+JQ7M8CgqKxMRrR2TTKHLbBsiUbdQs=N_bN=Uv7d9OqbTbXLw@mail.gmail.com>
In-Reply-To
<ZGQr03G/9swNcHt0@tapette.crustytoothpaste.net>

On Wed, May 17, 2023 at 12:24 AM Tim Walter (Visual Concepts) <twalter@vcentertainment.com> wrote:

Show 7 quoted lines
>
> it's SSD, actually NVme, and the PC is 128GB ram 64 core very fast.
> Both drives are local SSD drives, the working directory on D: and the repo on F:.
> the 3 hour thing is not a problem as such  (it's a little frustrating that git is single threaded, but regardless, this is not the issue I am concerned with)
> it's only 3 hours once, on the very first git add when I create the repo
> I can live with that, I was just giving context.
>

I've worked on large repos (100k+ files) and 3 hours sounds unreasonable to me. That's what, 27.7 mb/s? My guess would probably also be anti-virus or some privilege management type software.

Maybe try using procmon while you init and monitor all the processes to get a better understanding of what could be the problem https://learn.microsoft.com/en-us/sysinternals/downloads/procmon I've used that successfully in the past to figure out the source of unexplained performance problems (spoiler: it was privilege management)

Previous: brian m. carlsonNext: Tim Walter (Visual Concepts)
Message 5 of 6 in “git hangs with --separate-git-dir”
  1. Tim Walter (Visual Concepts)May 16, 2023
  2. brian m. carlsonMay 16, 2023
  3. Tim Walter (Visual Concepts)May 16, 2023
  4. brian m. carlsonMay 17, 2023
  5. Erik Cervin EdinMay 17, 2023
  6. Tim Walter (Visual Concepts)May 17, 2023

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.