[lc64]

That's a very rigorously written article.

Let's also note the 4x speed increase on windows 10, once again underlining just how slow windows filesystem calls are, when compared to direct access, and other (kernel, filesystem) combinations.

[wolfi1]

maybe the malware detection program adds to the performance as well

[cjblomqvist]

NTFS is really horrible handling many small files. When compiling/watching node modules (easily 10-100k files), we've seen a 10x size difference internally (same hardware, just different OSes). At some point that meant a compile time difference of 10-30 sec vs 6-10 min. Not fun.

[chefandy]

Their "windows dev drive" setup addresses this. I haven't tested it myself but I saw a couple of inexpertly executed tests showing significant performance gains. I honestly have no idea if my compile times are quicker.

[OttoCoddo]

With the right code, NTFS is not much slower than ext4, for example. Nearly 3% for tar.gz and more than 30% for a heavily multi-threaded use like Pack.

https://forum.lazarus.freepascal.org/index.php/topic,66281.m...

[alexhornby]

https://news.ycombinator.com/item?id=18783525 has previous discussion on why windows filesystem is slow

[nextaccountic]

But is it faster than accessing the filesystem with io_uring as well? I feel like this article should be updated

[nullindividual]

io_uring/IOCP won't change how long it takes to access a file.