MicrosoftJamesKehr I would never make unfounded accusations.
I have done network testing for decades. And iPerf is just one of the tools in the toolbox. I think you are completely missing the point. I always try to use something that is acting like the applications I am going to run on all the systems in the network to get a fair idea of the network performance. If I was just interested in saturating the network a simple flood ping would do the trick, but that does not tell me much. Just like a specially crafted piece of software from the OS vendor will not tell me much. If I was going to create a piece of software, that runs on all the nodes, it would most likely not match anywhere near the performance from ntttcp. And if my applications happens to runs worse on a windows system than on a Mac, fine, I can live with that. But I would like to know that, so I do not spend time looking for bottlenecks in the network. If iPerf3 used MSYS2 it would perhaps perform better, so perhaps MS should make a pull request.
I guess it depends on what the goal is. If my goal was to show off the theoretical throughput maximum of Windows, I would probably use ntttp. (Or ping flood).
