Adding file I/O would allow iperf to check of the bottleneck was the network or
the disk.
This should be for both the client and server, and should support /dev/zero and
/dev/null as files,
and also maybe reading from stdin and writing to stdout too.
Looks like the "-F" flag is available for this.
Original issue reported on code.google.com by bltier...@es.net on 14 Aug 2013 at 5:57
Original issue reported on code.google.com by
bltier...@es.net
on 14 Aug 2013 at 5:57