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

Re: Git status takes too long- How to improve the performance of git

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Nov 15, 2016, 15:10 UTC
Message-ID
<20161115151009.GB7854@book.hvoigt.net>
In-Reply-To
<1479202392275-7657456.post@n2.nabble.com>
On Tue, Nov 15, 2016 at 02:33:12AM -0700, ravalika wrote:
> Number of files - 63883

Since you also posted this to the "Git for Windows" mailinglist I assume that you are using Windows. Reduce the number of files. For example split the repository into two one for documentation and one for source. Thats what I did with a converted repository that had to many files.

Windows is unfortunately very slow when it comes to handling many files and if I recall correctly ~30000 files was in a nicely handleable range for a Git repository on Windows, but that might have changed...

Cheers Heiko
Previous: Christian CouderNext: MaryTurner
Message 4 of 6 in “Git status takes too long- How to improve the performance of git”
  1. ravalikaNov 15, 2016
  2. Fredrik GustafssonNov 15, 2016
  3. Christian CouderNov 15, 2016
  4. Heiko VoigtNov 15, 2016
  5. MaryTurnerNov 24, 2016
  6. Fredrik GustafssonNov 16, 2016

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.