From: ravalika <prenuka@gmail.com>
To: git@vger.kernel.org
Subject: Git status takes too long- How to improve the performance of git
Date: Tue, 15 Nov 2016 02:33:12 -0700 (MST) [thread overview]
Message-ID: <1479202392275-7657456.post@n2.nabble.com> (raw)
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 reply other threads:[~2016-11-15 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 9:33 ravalika [this message]
2016-11-15 10:24 ` Git status takes too long- How to improve the performance of git Fredrik Gustafsson
2016-11-15 11:44 ` Christian Couder
[not found] ` <CAEAva_1JAu+kWmk3MZDFK=4CgQB5M+JN8FwzMVr6zKgXTAhdXw@mail.gmail.com>
2016-11-16 13:21 ` Fredrik Gustafsson
2016-11-15 15:10 ` Heiko Voigt
2016-11-24 8:38 ` MaryTurner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1479202392275-7657456.post@n2.nabble.com \
--to=prenuka@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).