News for hackers. Stuff that matters.
Re:Fast Transaction Log: Windows by PaulHoule on Wednesday July 13, 2016 @10:09AM (#12086239)
Windows is fast at some things and slow at some things.

For instance, metadata reads on the filesystem are much slower on Windows than Linux, so it takes much longer to do the moral equivalent of "find /"

Circa 2003 I would say the Apache Web Server ran about 10x faster on Linux than Solaris, but that a Solaris mail server was 10x faster than the Linux server.

Turns out that Linux and Apache grew up together to optimize performance for the forked process model, but that fsync()-and-friends performance was much worse than Solaris at that time, if you want to meet specifications for reliable delivery.

Re:Fast Transaction Log: Windows by corysama on Wednesday July 13, 2016 @10:58AM (#12086638)
https://news.ycombinator.com/item?id=11864211 contains an interesting discussion from the author of PyParallel about how doing IO on NT in the style preferred by Linux is slow. This leads people to believe "NT IO is slower than Linux". However, doing IO on NT in the style preferred by NT is faster than Linux doing it's preferred thing.
Re:Fast Transaction Log: Windows by Analemma_ on Wednesday July 13, 2016 @12:02PM (#12087258)
That discussion and others have led me to the conclusion that the NT kernel has an excellent design and a subpar implementation (since only Microsoft's team can work on it), whereas Linux has a crappy design and an excellent implementation (being constantly refined and iterated by anyone). Kind of makes you wonder what could be possible if Microsoft would ever open-source it.
Re:Fast Transaction Log: Windows by walkingolof on Wednesday July 13, 2016 @03:35PM (#12089002)
"constantly refined and iterated by anyone"

Thats the theory, if you remove device driver folks, how many really works on the Linux kernel ?

Re:Fast Transaction Log: Windows by JonathonW on Wednesday July 13, 2016 @04:51PM (#12089567)
Here's [1] the current block I/O code from the kernel, annotated with the authors who last touched each line.

While I don't have time right now to actually go and count the number of distinct people involved, that's a lot of hands that have touched that source file over the years. And this view's only showing the changes that make up the current version of that file-- there are authors not credited there because their code has since been overwritten or edited by someone else.

[1] https://github.com/torvalds/linux/blame/master/block/bio.c

Re:Fast Transaction Log: Windows by tobias3 on Wednesday July 13, 2016 @01:05PM (#12087785)
Often the file system performance is also measured while an on-access virus scanner is active on Windows while measuring/testing the same thing on Linux without on-access scanner.

At that point one is comparing apples and oranges.

Re:Fast Transaction Log: Windows by vardump on Wednesday July 13, 2016 @02:14PM (#12088395)
From a practical point of view, what use is performance you can't practically benefit from?

If it's not performing well for your typical users using typical systems, it's not performing well. Those systems aren't going to change.

Those who engineer the system need to just work around the system specific limitations. Like a virus scanner.

Re:Fast Transaction Log: Windows by rasz_pl on Wednesday July 13, 2016 @12:56PM (#12087703)
as an anecdote many programs are way faster under wine than on real windows due to linux filesystem handling