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

Re: Debugging git-commit slowness on a large repo

From
Thomas Rast <trast@student.ethz.ch>
Date
Dec 20, 2011, 09:23 UTC
Message-ID
<87wr9rk35n.fsf@thomas.inf.ethz.ch>
In-Reply-To
<CB152498.2D6DB%joshua.redstone@fb.com>
Joshua Redstone <joshua.redstone@fb.com> writes:
> As a bonus, I've also profiled git-add on the 1-million file repo, and it
> looks like, as you might expect, the time is dominated by reading and
> writing the index.  The time for git-add is a couple of seconds.

Note that the time to write the index itself is also rather small, but the time needed to sha1 the index when loading and then again when saving it really hurts.

(I noticed this while working on the commit-tree topic.)
-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Joshua RedstoneNext: Joshua Redstone
Message 14 of 16 in “Debugging git-commit slowness on a large repo”
  1. Joshua RedstoneDec 2, 2011
  2. Carlos Martín NietoDec 3, 2011
  3. Junio C HamanoDec 5, 2011
  4. Joshua RedstoneDec 7, 2011
  5. Nguyen Thai Ngoc DuyDec 7, 2011
  6. Joshua RedstoneDec 7, 2011
  7. Nguyen Thai Ngoc DuyDec 8, 2011
  8. Joshua RedstoneDec 9, 2011
  9. Joshua RedstoneDec 9, 2011
  10. Joshua RedstoneDec 13, 2011
  11. Joshua RedstoneDec 20, 2011
  12. Junio C HamanoDec 20, 2011
  13. Joshua RedstoneDec 20, 2011
  14. Thomas RastDec 20, 2011
  15. Joshua RedstoneDec 20, 2011
  16. Tomas CarneckyDec 4, 2011

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.