Care to elaborate in windows busted network stack? Genuinely interested to read about it.
Two biggest ways
1. Busted receieve window
2. Still lacks a queue mechanism that can compare and do what fq-codel or cake does in linux. Both can control latency problems well compared to anything else we have in networking, neither are present in windows.
How windows lacks in other areas.
By not having a feature like napi polling latency on a socket can't be kept as low as possible when it comes to latency
Not all nic drivers are equal and users never know if their wifi has airtime fixes or their ethernet has drivers where the buffer rings for data won't cause bufferbloat
Some offloads are still busted and often is better to disable than leave enabled
Stateful packet inspection mechanisms in windows are still know to cause lag vs being disabled
Cannot effectively pin your processors to services or wield them as well as well bsd/linux. This matters as anything multicore is served better letting one or two processors do all the work. You gain a benefit seperating your upload and download traffic on different cores in same numa node. Ideally if you 8+ thread 4 threads for each aspect of data transfer in networking would be best.
Recieve Side Scaling is still busted and only engages in high bandwidth transfers. In other OS you can have better implementations or feature that do the same regardless of network load
it's 2020 and it's pathethic that fixes meant at the start of the last decade for other OS aren't in MS premier desktop or console kernels.