3 ms·
IO performance is atrocious. git status on a Linux tree takes a 10s of seconds.
by stefan_ 8y ago
IO performance is atrocious. git status on a Linux tree takes a 10s of seconds.
- ivan_gammel 8y agoGit works perfectly in PS, why would you need to run it in WSL?
- squeaky-clean 8y agoNot the original commenter, but I do everything else in bash, and zero things in PS. Why would I want to remember which shell runs which program best?
- ivan_gammel 8y agoThat makes sense, however if you are Windows user, bash is not an obvious choice for primary shell there.
- sigzero 8y agoI don't think that is correct. If you install WSL you are not a typical Windows user.
- ivan_gammel 8y agoI didn't mention "typical" Windows user. WSL will always be a second-class citizen in Windows, so if you are power user trying to improve your performance, what's the point in choosing a second-class solution after choosing this OS? Learning one more shell, just like learning one more programming language, has some benefits.
- squeaky-clean 8y agoBecause I like Windows for myself but my company uses Linux based servers and bash as our shell. It's not just about ME switching to PowerShell, but getting 30 other people to do it too. Not gonna happen.
- stefan_ 8y agoBecause compiling the Linux kernel doesn't? And well, that's another big thing with WSL, you can't share files.
- edaemon 8y agoI don't know when you last tried it, but IO performance is much better in the new (Fall Creators Update) version. I had the same problem with git status but after updating it's much quicker. Things also seem like they're faster in the WSL file system than when you're using WSL in the Win32 file system.
- city41 8y agoIt is much better (and even better if you disable Windows Defender on your WSL stuff), but it's still not nearly as fast as actual Linux. I switched from WSL to a Linux VM primarily due to IO still being slow enough to be a problem for me.