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

Re: git performance after directory copy

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Sep 20, 2010, 09:45 UTC
Message-ID
<4C972D49.9040306@drmicha.warpmail.net>
In-Reply-To
<C5A8FDEFF7647F4C9CB927D7DEB307730F33B7C9@ahr075s.basler.corp>
Gaer, A. venit, vidit, dixit 20.09.2010 11:20:
Show 11 quoted lines
> Hello all,
> 
> while moving a project directory around I stumbled over an interesting
> phenomenon. On a copied source directory "git status" seems to be about
> 3 times slower than on the original directory. Only after a "git reset"
> both copies behave the same again. Is this connected to the timestamps
> of files & directories? Actually I would like to move the project
> directories of several software developers to a new partition and
> forcing them all to "git reset" in all of their repos is a little bit
> annoying. Any suggestions how to "repair" the repos less intrusive?
>

Since you clone from A to B, then copy from B several times, why don't you clone from A several times instead?

If it's really about moving across file-system boundaries, then I don't think there's a way around: you need to refresh the index with the changed inodes information.

Michael
Previous: Gaer, A.Next: Matthieu Moy
Message 2 of 8 in “git performance after directory copy”
  1. Gaer, A.Sep 20, 2010
  2. Michael J GruberSep 20, 2010
  3. Matthieu MoySep 20, 2010
  4. Michael J GruberSep 20, 2010
  5. AW: git performance after directory copyGaer, A., Sep 20, 2010
  6. Johannes SixtSep 20, 2010
  7. AW: git performance after directory copyGaer, A., Sep 20, 2010
  8. Matthieu MoySep 20, 2010

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.