----- Original Message ----- 
  From: Stephen Morton 
  To: Git for human beings 
  Cc: philipoak...@iee.org 
  Sent: Wednesday, February 01, 2017 8:28 PM
  Subject: Re: [git-users] How to improve the Git status performance


  On Wednesday, 1 February 2017 00:42:51 UTC-5, Ravalika wrote:
    Thank you Philip and Mark.


    We are using Linux servers. We can't have local disk, as it is corporate 
setup. 
    We have our project shares on build servers across LAN only


    I have tried sparse checkout and other options but not much improvement on 
git status. 
    git status -uno
    git update-index --untracked-cache and git update-index --split-index




  Sounds to me like the issue is "git status performance when repo is on a 
network drive".
  What you will need to do is this
    - Find out what sort of network mounting you have
    - Find out what sort of caching you have, and what is available to you.
    - You started to do some profiling on 'git status' performance that seems 
to indicate that caching plays a big part. You could confirm this by observing 
how subsequent 'git status' commands are faster, but that when you drop the 
cache, performance goes back down to the original slow time.
    - Talk to your IT people to find out if anything can be sped up.
    - Do some research on git's performance in this situation


  My gut feeling is that you are basically out of luck. Git does a lot of 
filesystem calls and I suspect that performance on a repo with lots and lots of 
files is going to be extra-slow when network mounted. (By contrast, my huge 
corporate repo on a locally-mounted SSD on linux can do a 'git status' in 
<0.1s.)



  Steve
Also, talk with your IT to determine if you can get some local machine space to 
host your local copy (then just use push to the server repo for one shot 
updates and 'backup'). Explain that it's the way Git was designed - to allow 
local working when off network. Failing that, use it as a lever to improve the 
network performance.

Philip

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to