[qz2]

That’s even worse. File system performance is so terrible that it’s unusable for anything past trivial operations. AFAIK it maps the Linux ABI/syscalls to NT and that’s it. So you get the dire small file performance of NTFS to contend with (MFT locking).

Wherever you go there are puddles of this ick to stand in.

I’ve been at this long enough to know when to give up and walk away.

[dylan604]

Slightly tangential at best, but there was software I used to use in a former life that was developed and designed for Linux systems first. They were then able to cross compile it for Mac and Windows. When first using the software, it was only ever used on Windows. Once I started using it in more advanced ways, I wanted to try out the Mac and/or Linux versions since they had a CLI client. Both of these systems ran circles around the Windows version in how much faster they were to do the exact same processing. Turns out, they were using the same C-style calls to access files. That C-style code is very slow on windows, yet using a Windows native call brought their software to the same speed.

TL;DR Windows definitely has its own way of doing file system access