4 ms·
That'll probably be NTFS shafting you. It's terrible at handling small files. Trick I found was to fire up a Linux VM and do your compilation in there.
by baz00 3y ago
That'll probably be NTFS shafting you. It's terrible at handling small files.
Trick I found was to fire up a Linux VM and do your compilation in there.
- wongarsu 3y agoAlso Windows file handling in general. It's incredibly flexible, allowing an arbitrary number of drivers to log or modify every disk access. That's great if you want real-time antivirus software, transparent file encryption (without encrypting the full partition), data-loss prevention software, advanced file syncing etc. But it also makes workflows that access lots of small files very slow. Instead of a VM you can also use WSL2, assuming you put the files in the linux file system instead of accessing the host file system. (Yes, technically that's also just a fancy VM running in Hyper-V; but it's a more integrated experience than e.g. VMWare)
- distract8901 3y agoYeah, granted the server is running a zfs pool on 7 mechanical SAS drives. But the windows machine has an nvme drive so I thought it'd even out. Looking into compiler optimization, I can tell it's a very deep rabbithole that I'd rather stay away from if at all possible
- distract8901 3y agoI actually hadn't even thought of that. I'll have to see what performance on a VM is like these days, maybe it'll be enough to do my normal daily work? Last time I tried that was back in the windows 7 days and VMs were almost unusable.
- baz00 3y agoIf you provision the whole disk up front i.e. reserve space then it'll be near native. That applies to Hyper-V, VMWare Workstation and VirtualBox VMs. WSL this is not necessarily the case. I don't use WSL for a number of reasons including that.