Linus Torvalds <torvalds <at> linux-foundation.org> writes: > Doing an 'lstat()' on every single file in the tree would tend to do that > to you, yes. Even with a fast network and a good NFS server, we're talking > millisecond-range latencies, and if your tree has tens of thousands of > files, you're going to have each "git diff" take several seconds. Is there any way to improve 'git status' performance on nfs? I know nothing about how that code works, but if it's strictly serial, i.e. it waits for the result of each lstat() before doing the next lstat(), then perhaps it could be sped up by overlapping the lstat() calls via multi threading. Reason I ask is that at my work place, using only local disks would be difficult. We run lots of long running tests in a server farm, and working on nfs allows the compute servers to access our data transparently. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
