Hi 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 ...
Hi Bruce, Thanks for your informative post. I'm skeptical that posix
emulation is the bottleneck for these capacity tests. One can run iperf3
-c localhost and iperf3 -s to check. CPUs tend to run sub nanosecond and
from internal cache so this should be fine and off board network i/o is
going to be m...
Hi James and everyone else in this thread – Bruce Mah here, one of the
developers of iperf3 at ESnet. We’ve heard from a lot of people about
this blog post and been following the back and forth. Thank you for all
the updates to the original post, to iperf.fr for removing the old
Windows iPerf3 binar...
Sure, for MSFT only then MSFT tools are fine. Most networks now are a
mix requiring tools that run on all platforms and systems. Iperf3 is
designed for capacity tests and does say use iperf2. Yet most still use
Iperf3 because 3 is larger than 2 and they don't understand the
technical differences. Yo...
@rjmcmahon Please keep in mind that I am in support, so the article is
support slanted. From a Microsoft supportability perspective, we need
internally trusted tools like ntttcp and ctsTraffic that we (Microsoft
support) can use for troubleshooting purposes when addressing networking
issues related ...
Latest Comments