![]() ![]() ![]() 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. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |