Comment by rstat1
12 hours ago
I'd wager that's more likely due to Windows than the hardware. Like sure the hardware does play a part in that but its not the whole story or even most of it.
My C++ projects have a python heavy build system attached where the main script that runs to prepare everything and kick off the build, takes significantly longer to run on Windows than Linux on the same hardware.
Afaik a lot of it is ntfs. It’s just so slow with lots of small files. Compare unzipping moderately large source repos on windows vs. POSIX, it’s day and night.
No, it’s not NTFS, it’s the file system filter architecture of the NT kernel.
I had internalised that it was Windows Defender hooking every file operation and checking it against a blacklist? I've had it forced off for years.
Just deleting 40,000 files from the node_modules of a modest Javascript project can thoroughly hammer NTFS.
I think part of that is Explorer, rather than NTFS. Try doing it from the console instead. rd /q /s <dir>.
4 replies →