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

Git very slow ?

From
KMKen Moffat <zarniwhoop@ntlworld.com>
Date
Mar 7, 2015, 01:30 UTC
Message-ID
<20150307013007.GA13250@milliways>

Hi, please CC me if that is not your usual fashion, because I am not subscribed.

I use git for my build scripts - those are accessed over nfs. Since I started using 2.1 and later (I don't think I used 2.0) commands such as 'commit' take a long time before anything happens. I assumed that the newer version meant this would take longer.

But today^Wyesterday I was bisecting the kernel on a local filesystem - even when the number of revisions left to test was in the single digits, git bisect took a long time to decide which revision should be the next one to test. The filesystems are ext4. Is this sort of delay normal now?

What really prompted me to ask is that I ran git blame on a script, to see when I made a particular change so that I could add that information to a ticket, and almost gave up waiting because it felt as if it was taking for ever.

ĸen
-- 
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
Next: Kevin D
Message 1 of 9 in “Git very slow ?”
  1. Ken MoffatMar 7, 2015
  2. Kevin DMar 8, 2015
  3. David KastrupMar 8, 2015
  4. Ken MoffatMar 8, 2015
  5. David KastrupMar 8, 2015
  6. Linus TorvaldsMar 8, 2015
  7. Ken MoffatMar 8, 2015
  8. Linus TorvaldsMar 8, 2015
  9. Ken MoffatMar 8, 2015

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.