MicrosoftHi Bob--
I'd be the first to admit that I don't understand the UNIX / POSIX type runtime environments (e.g. WSL/WSL2/Cygwin) under Windows well enough to have an educated opinion on where the bottlenecks might be. (I've been learning from reading this blog post and comments however, thanks again to everyone who's posted.)
I think that using Microsoft's proprietary tools can be useful in certain scenarios, such as an all-Windows environment, perhaps for doing some kind of specialized measurements or troubleshooting that are specific to that particular platform. But as you've pointed out, tools like iperf2 and iperf3, using industry standard APIs, are needed for the cross-platform environments that many users live in, as well as being able to compare results across different OS platforms.
Bruce.
It would also be great if the recommended tools is available.
The Linux version on github has 1(one) release made in 2019, as source. So not easy to use, and I would also doubt the release can compile, and you need dependencies to do that. There are issues registered on the repository.
So unless Microsoft releases binaries, packages or similar, we will all continue using the tool iperf2 and iperf3 we know.
