3 ms·
Also 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
by wongarsu 3y ago
Also 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