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

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

From
Rravalika <prenuka@gmail.com>
Date
Nov 15, 2016, 09:33 UTC
Message-ID
<1479202392275-7657456.post@n2.nabble.com>
Hi All,

We are using git-1.8.2 version for version control. It is an centralized server and git status takes too long

How to improve the performance of git status
Git repo details:

Size of the .git folder is 8.9MB Number of commits approx 53838 (git rev-list HEAD --count) Number of branches - 330 Number of files - 63883 Working tree clone size is 4.3GB

time git status shows real 0m23.673s user 0m9.432s sys 0m3.793s

then after 5 mins real 0m4.864s user 0m1.417s sys 0m4.710s

And I have experimented the following ways 
-          -  Setting core.ignorestat to true
-          -  Git gc &git clean
-          -  Shallow clone – Reducing number of commits
-          -  Clone only one branch 
      - Git repacking - git repack -ad && git prune
-     - Cold/warm cache 

Could you please let me know, what are the ways to improve the git performance ? I have gone through the mailing lists.

Thank you, Renuka

-- View this message in context: http://git.661346.n2.nabble.com/Git-status-takes-too-long-How-to-improve-the-performance-of-git-tp7657456.html Sent from the git mailing list archive at Nabble.com.

Next: Fredrik Gustafsson
Message 1 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.