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

Re: git-blame extremely slow in partial clones due to serial object fetching

From
MKManoraj K <kmr.manu535@gmail.com>
Date
Nov 20, 2024, 11:59 UTC
Message-ID
<20241120115910.45681-1-mkenchugonde@atlassian.com>
In-Reply-To
<B010051F-B182-4DB8-9469-AA2F53781968@shopify.com>
Hi Burke,
> When running git-blame in a partial clone (--filter=blob:none), it fetches
> missing blob objects one at a time. This can result in thousands of serial fetch
> operations, making blame extremely slow, regardless of network latency.

We are also experiencing this issue with partial clones. Have you found any workarounds since reporting this?

Git team - would appreciate any insights or suggestions on handling this performance bottleneck in the meantime.

Best regards, Manoraj K

Previous: Burke LibbeyNext: Jonathan Tan
Message 2 of 10 in “git-blame extremely slow in partial clones due to serial object fetching”
  1. Burke LibbeyNov 19, 2024
  2. Manoraj KNov 20, 2024
  3. Jonathan TanNov 20, 2024
  4. Junio C HamanoNov 20, 2024
  5. Han YoungNov 21, 2024
  6. Shubham KanodiaNov 22, 2024
  7. Junio C HamanoNov 22, 2024
  8. Shubham KanodiaNov 22, 2024
  9. Jonathan TanNov 22, 2024
  10. Junio C HamanoNov 25, 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.