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

Re: [git-users] worlds slowest git repo- what to do?

From
Duy Nguyen <pclouds@gmail.com>
Date
May 17, 2014, 01:49 UTC
Message-ID
<CACsJy8CmyJbUGAfb7SaAo5aNwOrJ8iwUtxZgQTAANChOsaWCRA@mail.gmail.com>
In-Reply-To
<537681A4.2070601@gmail.com>
On Sat, May 17, 2014 at 4:22 AM, John Fisher <fishook2033@gmail.com> wrote:
Show 6 quoted lines
>> Probably known issues. But some elaboration would be nice (e.g. what operation is slow, how slow, some more detail
>> characteristics of the repo..) in case new problems pop up.
>
> so far I have done add, commit, status, clone - commit and status are slow; add seems to depend on the files involved,
> clone seems to run at network speed.
> I can provide metrics later, see above. email me offline with what you want.

OK "commit -a" should be just as slow as "add", but as-is commit and status should be fast unless there are lots of files (how many in your worktree?) or we hit something that makes us look into (large) file content anyway.

-- 
Duy
Previous: John Fisher
Message 5 of 5 in “Re: worlds slowest git repo- what to do?”
  1. Philip OakleyMay 15, 2014
  2. Sam VilainMay 15, 2014
  3. Duy NguyenMay 16, 2014
  4. John FisherMay 16, 2014
  5. Duy NguyenMay 17, 2014

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.