![]() I didn't even notice the performance hit across OS file systems.īut lately something was bothering me. My main reason for switching to WSL2 was much better Linux support (kernel and syscall stuff), and for a long time everything was fine. While I have experimented already with WSL 1 for some time, I switched to WSL 2 since it became generally available in Windows 10 Version 2004 (apparently it was backported to 19). The reason why it is possible, specifically if you do have Linux focused projects, is WSL (Windows Subsystem for Linux). While I still have my Linux on another hardrive, I haven't booted into it for half a year now. And to my own surprise nowadays solely on my Windows 10 installation. ![]() Here's a tip to speed up git status again.įor personal projects I work on my PC. OS X (using lldb with a breakpoint on lstat64):ġ: name = 'lstat64', locations = 1, resolved = 1, hit count = 103859ġ.1: where = libsystem_kernel.With WSL2 filesystem performance degraded for the mount points of the Windows host. I traced it down to on Linux we are only making ~700 lstat syscals but Tl dr Do you know why by default `git status` is trying to `lstat`Įvery file in the repo on OS X but not on Linux? And is that config Performance was an order of magnitude slower on OS X than on Linux. ![]() I'm working on a git repo for my company and noticed that `git status` ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |