Three Reasons Why You Should Not Use iPerf3 on Windows

I am working my way through a full across the board implementation of iperf3, utilizing Kotlin Multiplatform, for all platforms.

https://github.com/jerryabramson/iperf3-kmp

The iperf3 code is linked in using the different platforms shared library techniques (NDK+JNI on Android, JNI on Desktop, cinterop on iOS)

• On desktop there is a GUI and a CLI.

All platforms are supported natively at this point, although the Windows version forks off an iperf3.exe (and the iperf3.exe is x86_64 only).

This skews the windows results dramatically and is a major problem.

I am part way through a real port of iperf3 to Windows (no Cygwin64, no Msys). 

I cannot take credit for the Windows port, since there is already a developer who got part way through the exercise, but then seems to have abandoned it:

https://github.com/Active-Software/iperf3-windows-msvcf

With some tweaking I was able to get the above code base building natively on Windows on Arm as well!