4 ms·
It's the file system filters that are an issue on Windows. It trades performance for extensibility. NTFS itself is a fast file system.
by 0x1d7 4mo ago
It's the file system filters that are an issue on Windows. It trades performance for extensibility.
NTFS itself is a fast file system.
- wahern 4mo agoeBPF has opened the door to such bloatware on Linux. Previously there was no easy, stable way for enterprise bloatware vendors to maintain complex file and subsystem filter and analytic modules. Now that market is exploding because of eBPF, and it's a big reason there's so much work around growing eBPF's capabilities.
- throwa356262 4mo ago"NTFS itself is a fast file system" File access is significantly slower on Windows compared to Linux on the same hardware. You can run Linux inside a VM and it will easily beat the host OS in filesystem performance. If the problem is not NTFS, then it is in how the Windows OS uses it
- tssva 4mo ago> If the problem is not NTFS, then it is in how the Windows OS uses it Isn't that exactly what the comment you are replying to is saying?
- 0x1d7 4mo agoThis is correct. The flexibility of the file system filter model does have a performance penalty and you will see that across file systems. This is why 'DevDrive' exists for ReFS, to reduce that penalty (though ReFS comes with it's own, namely in write performance due to journaling). The model wasn't a big deal back in the day of IDE and SCSI, but it certainly shows on flash storage.
- NoGravitas 4mo agoThis is what I keep hearing. However, I have never had the good fortune of using a Windows installation where NTFS was allowed to be fast.