3 ms·

Have you seen this comment from a Microsoft employee explaining why NTFS performance is so bad? It's pretty interesting and informative, but doesn't leave me wi

Have you seen this comment from a Microsoft employee explaining why NTFS performance is so bad? It's pretty interesting and informative, but doesn't leave me with much hope that things will ever improve. https://github.com/Microsoft/WSL/issues/873#issuecomment-425272829 https://github.com/Microsoft/WSL/issues/873#issuecomment-425... I use Windows for development at work (semi-voluntarily - our Windows support was getting neglected because most developers choose to use run macOS or Linux), and I've been getting pretty fed up with how slow it is. And it's not just filesystem performance; process creation and terminal output are horrendously slow as well. The only redeeming thing about development on Windows is that Linux doesn't have any debuggers that are as good/usable as Visual Studio.

setquk 8y ago
I’ve seen that and it misses the mark by a mile because the main performance constraint is MFT contention. You can see this because the tools suck just as bad on native windows as on WSL without that in between. Check out 10,000 small files on (1) NT native SVN, (2) WSL on Windows, (3) Linux on ext4. 1 and 2 are within 10% of the time delta. 3 is 10x faster at average. At this point I reckon they won’t fix NT but close the gap on NT and forget to mention the MFT problem. I’ve dealt with this issue going back 20 years since NT4 for ref.
CountSessine 8y ago
Very interesting post - thanks for sharing it. Filter drivers and IRPs really are the worst architectural blunder MS made in Windows. They took what really should be a corner-case (driver interposition) and put it on the development path of every hardware driver programmer to trip over. We got KMDF eventually, but that took years...