Re:Arranging Invisible Icons in Quadratic Time
by muststopmyths on Tuesday February 16, 2021 @09:47AM
(#26154283)
> TCP performance and network latency in general was always worse on Windows
I would disagree. Unless you're trying to write "cross-platform" network code using select and other POSIX-style interfaces, in my experience Windows with IOCP or RIO will beat any other user mode application TCP stack for I/O rates and latency.
Vista's stack had latency issues in the beginning but Windows 8 with RIO was released a long time ago.
Note I said "user mode application". Linux has easier kernel bypass and well-supported DPDK for applications that really need it. You obviously cannot beat that with user-mode code
Re:Arranging Invisible Icons in Quadratic Time
by dblohm7 on Tuesday February 16, 2021 @12:35PM
(#26156439)
Yeah, IME Windows really excels if you build a TCP server using the async winsock2 APIs + IOCP.
Where people get into trouble with it is when they try to code against it like it's another Unix variant.
In the past? It was a bit of a mixed bag. TCP performance and network latency in general was always worse on Windows than Linux, largely for silly reasons. Similarly, the 32-bit versions had a lot of fixed sized memory regions for things like file caching that were set in stone in the NT4 era and not changed until Windows Vista. Towards the end when all 32-bit machines had 4GB of memory, this made disk access unnecessarily slow.
There are also design space differences between Linux and Windows. On Linux a process is very lightweight, basically a fat function call. On Windows the equivalent need is typically met by RPC calls to an already running process. Threads are cheap on Windows and threading was very well supported since the 1990s. On Linux, not as well, even now. For example, even NT4 and async scatter/gather IO that SQL Server used back in v7. I believe that Linux is still struggling with this.
Conversely, Windows beats the pants off Linux in some areas, even now. Try using a Linux desktop with a flaky DNS server. Hooo-boy. Timeout city! On Windows this is almost unnoticeable, because it fails over to the secondary DNS server in milliseconds and caches all results as expected. Linux failover and caching seems to require a significant effort to set up by the users, for some mysterious reason.
Similarly, Windows SMB v3 over RDMA is crazy fast. If you have the right NIC, you can flatline a 40 Gbps pipe with a single file copy. In the Windows Explorer GUI! No special tools needed. Copy, paste, and next thing you know you're doing 5 gigabytes per second. That takes real effort to match in Linux.
Etc...
Basically, everyone is used to the warts on their preferred system, and has learned to work around them. But when exposed to something unfamiliar, all the little issues seem to be always in the way.