Re:Mononoke – A Mercurial source control server designed to ...
by alexeiz on Monday March 12, 2018 @12:58PM
(#16569507)
If you're working with a Git repo on a remote filesystem, you're doing it wrong. Git is not designed for remote filesystems. It relies on certain file operations to be extremely fast. So Git works best with local filesystems. With Git, you want to clone the entire repository locally and work with it locally. That's the idea behind the distributed version control: every committer has the entire copy of the repository. With a remote filesystem you're effectively centralizing your repository.
[ Parent
| on HN ]
Re:Mononoke – A Mercurial source control server designed to ...
by daemin on Tuesday March 13, 2018 @05:25AM
(#16574726)
Yeah, the git metadata is on a remote file server, that's the entire point of the Microsoft file system extensions for running a huge git monorepo. The code and assets you are working on is local, but the history and other metadata elements are stored remote and lazy loaded.
So if you're remote file server is relatively close it doesn't matter too much and the lag is not noticeable, but if it's across the country or across the world...