I've used Linux VMs on Windows before - VMWare Workstation has been around for over a decade and has a lot of bells and whistles that make the experience tolerable, but again, the IO is too slow to share Windows and Linux apps between filesystems, so you're basically forced to develop 100% in the VM, IDE included. would grind Jetbrains on Windows to a halt as it simply couldn't sync with the project files on Linux due to slow IO. Trying to use a polyglot project with a bunch of Java, Scala, Go, various plugins like DB views, etc. I tried this on WSL1 and it absolutely didn't work for any project larger than the typical Hello World example. So I hope someone still working that nice seamless syscall layer for a future WS元. I agree with the other posters here that the WSL1 approach seemed far more elegant, and probably the only way to "not see the joins"- with WSL2 we're worrying about filesystem boundaries _and_ memory now, probably forever. WSL2 will also quite happily gobble so much memory that Windows slows to a crawl (especially filling Linux's disk buffers on file copies) - that seemed like an odd default, - you just have to pop a. For me (doing fs-intensive Rails development), this was a big win. The switch to a VM flipped this relationship round - so now the formerly native / NTFS side is the second-class citizen, but you get the expected performance when putting your files on the "Linux side". running a big test suite, or a git checkout felt really incredibly slow. That meant that people doing disk-intensive workloads on the Linux side noticed a big slowdown compared to a native Linux system - certainly e.g. My understanding was that there were some hard-to-impossible problems to solve to really accelerate the filesystem access from the Linux side under WSL1. I think I'll be deconverting my various WSL distributions because the performance hit was too much, it just was absolutely unbearable to even run simple commands in my Windows side. But for daily driver mixed OS use, WSL2 has made me very unhappy. WSL2 should definitely stick around and has use cases, for Docker it's unparalleled. It's very depressing because WSL1 is so, so promising and is so close to feature parity. Or "wsl npm install" or "wsl npm run test" or any of that. Now performance across the OS boundary is so bad, I wouldn't even think of using "wsl grep" in my C drive. One of the truly wonderous things about WSL1 was the ability to do something like this in a PowerShell window:Ĭ:\some-code-dir\> wsl grep -R "something" | Some-PowerShell | ForEach-Item The downside performance loss is, however, staggering for the files I had in C:\ĭon't even get me started on how long an npm install took. Yes, unzipping tarballs or manipulating and stat syscalls are cheaper now on the Linux side. WSL2 is a massive hit to the seemless experience between the two operating systems with filesystem performance from Linux to Windows files orders of magnitude worse. In WSL2, running the same command takes over 30 seconds. In WSL1, running "wsl git status" on a moderately sized repo on an NTFS (Windows side) drive or SMB file share is nearly instantaneous.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |