3 ms·
> partly because of working in the humongous Windows git, which of course seems to have similar issues to the Mozilla ones mentioned here such as auto-rebuild t
by masklinn 7y ago
> partly because of working in the humongous Windows git, which of course seems to have similar issues to the Mozilla ones mentioned here such as auto-rebuild tools
Also possibly because windows FS operations are known to be extremely slow. That's one of the issues many folks have with WSL too.
- WorldMaker 7y agoJust to be clear, by Windows git I meant `Windows.git`, the git repository for Windows itself which no one in the world has yet admitted to having a larger git repository. The repository that Microsoft built tools like GitVFS for to virtualize dealing with the git object database and even the full worktree to manage working with that repository. Local file system operations don't sound like they are the bottleneck there. (Also, Windows FS operations aren't "extremely slow" in general, they just have very different transactional model than Linux FS operations, which was the problem with WSL1 file operations trying to use the Windows FS to pretend to be the Linux FS, layering different transactional models on top of each other in a complex stack. Which is why WS2 is taking the VHD approach.)