←back to thread

Why is Windows so slow?

(games.greggman.com)
337 points kristianp | 2 comments | 19 Dec 11 06:56 UTC | HN request time: 0.423s | source
Show context
markokocic ◴[19 Dec 11 09:31 UTC] No.3369085[source]▶
I'm not sure if it is related, but the fact is that file system operation on windows are much slower that on Linux. I remembering that copying large ISO image from one windows partition to another windows partition using Total Commander under Wine on Linux was faster that doing it directly on Windows.

I also remember that I was able to create file copy utility in assembly as a homework assignment that was couple times faster than windows/dos copy command.

The only two reasons I can think of that explain this are: 1 - noone cares about windows fileystem performance. 2 - someone decided that it shouldn't be too fast.

replies(1): >>3369171 #
1. m_for_monkey ◴[19 Dec 11 10:15 UTC] No.3369171[source]▶
In Total Commander you can configure the buffer sizes used while copying. Maybe in your homework you chose the right buffer size too (and, of course, asm is fast, but hard to write, I'm sure you didn't bother too much with error checking and other "small" problems).

Moreover, the optimal buffer size is different for small and large files, maybe Windows is not optimized for large size like a DVD image.

replies(1): >>3369524 #
2. markokocic ◴[19 Dec 11 13:26 UTC] No.3369524[source]▶
As for Total commander example, that was out of the box experience, without any tweaks. I just wanted to point out that even when using emulation layer to access Windows native filesystem type, Linux was significantly faster on file system operations.

As for my homework "copy" command, I know that it is not fully replacement to file copy windows command, but if copy operations takes >10min, all those checks and additional tasks shouldn't make IO bound operation take couple time longer than what some student implemented as homework.