From: Erik Cervin Edin <erik@cervined.in>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Tim Walter (Visual Concepts)" <twalter@vcentertainment.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git hangs with --separate-git-dir
Date: Wed, 17 May 2023 09:11:39 +0200 [thread overview]
Message-ID: <CA+JQ7M8CgqKxMRrR2TTKHLbBsiUbdQs=N_bN=Uv7d9OqbTbXLw@mail.gmail.com> (raw)
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:
>
> 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)
next prev parent reply other threads:[~2023-05-17 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 17:54 git hangs with --separate-git-dir Tim Walter (Visual Concepts)
2023-05-16 21:30 ` brian m. carlson
2023-05-16 21:55 ` Tim Walter (Visual Concepts)
2023-05-17 1:20 ` brian m. carlson
2023-05-17 7:11 ` Erik Cervin Edin [this message]
2023-05-17 16:31 ` Tim Walter (Visual Concepts)
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='CA+JQ7M8CgqKxMRrR2TTKHLbBsiUbdQs=N_bN=Uv7d9OqbTbXLw@mail.gmail.com' \
--to=erik@cervined.in \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=twalter@vcentertainment.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).