title: Ways to improve git status performance
body: <p>I have a repo of 10 GB on a Linux machine which is on NFS. The first time <code>git status</code> takes 36 minutes and subsequent <code>git status</code> takes 8 minutes. Seems Git depends on the OS for caching files. Only the first <code>git</code> commands like <code>commit</code>, <code>status</code> that involves pack/repack the whole repo takes a very long time for a huge repo. I am not sure if you have used <code>git status</code> on such a large repo, but has anyone come across this issue?</p>
  
  <p>I have tried <code>git gc</code>, <code>git clean</code>, <code>git repack</code> but the time taken is still/almost the same.</p>
  
  <p>Will sub-modules or any other concepts like breaking the repo into smaller ones help? If so which is the best for splitting a larger repo. Is there any other way to improve time taken for git commands on a large repo?</p>