...
The value plotted for 3 TCP connections at 10000 Mbps uses no tc qdisc, just the 10GE links. A similar value was obtained for 5 TCP connections.
Recent testing (January 24 and 25), has produced two important findings:
- iPerf 2 has an unexpected dependency on the Units in the UDP -b Bandwidth #[KM] option configuration on the Client.
- the -b 972000000 and -b 972M options produce different sending rates. -b 972000000 seems to be correctly sending the target bandwidth.
- Neither iPerf 2 or iPerf3 can measure one-way and RT delay, and delay is a both critical measurement metric and a demanding requirement of most Edge Applications.
- the measurement tool "netprobe" can measure both loss and delay, and can supply measurements on every packet received. netprobe architecture is similar to iPerf, in that individual test streams can be launched from the Client to the Server (running as a daemon, if desired). netprobe is installed on Node 5 /home/opnfv/netprobe/netprobe2
Here are some windows with netprobe in operation, showing results:
