3 ms·

Especially when you have WSL

• rbanffy 2y ago
  Performance under WSL can be atrocious depending on which side of the machine your files live. It's OK if they are on the Linux side, but if they are on the Windows side, you'll access them as a network mounted file share. Not great if you open/close lots of files.
  • nickjj 2y ago
    Yep, I have an rsync script which I run from WSL to backup both my WSL home directory and a bunch of files on a separate Windows drive to an external hard drive. It takes something like 8 minutes for rsync to get the metadata about files before it starts potentially transferring anything. On native Linux a comparable amount of files takes less than 10 seconds.
    • rbanffy 2y ago
      The worst case scenario is when the data has to go over the WSL border twice (one to be processed by whatever Unix thing you are using) and another when it's written to an NTFS filesystem somewhere else. My personal happy space is actually Cygwin. It's Unixy enough and doesn't cross the WSL border. Not great because NTFS doesn't perform that well under it, but definitely better than WSL.
  • voidfunc 2y ago
    Have you tried the Dev Drive feature in Windows 11? It's still network mount but supposedly speeds things up.
  • ninkendo 2y ago
    Same thing with e.g. docker for macOS… it’s the primary reason I opted for running Linux on my dev machine at work. Using a virtualization layer to get docker/k8s/etc gives such abysmal performance it’s really crazy that it’s such a popular approach. I’m not even sure what I’d have to do if I used windows… how do people even use git nowadays? Run it in WSL with files shared to your editor in windows? Run git natively in windows? Is NTFS still dog slow scanning tons of small files? Is that “git bash” cygwin distro still the way to go? It sounds like a total mess.