[Make-wifi-fast] Fwd: iperf 2 "short term" road map

Toke Høiland-Jørgensen toke at redhat.com
Fri Jul 19 17:02:53 EDT 2019

Bob McMahon <bob.mcmahon at broadcom.com> writes:

> Hi Toke,
> Do let me know.  We're focused on the network i/o testing aspect (per being
> a WiFi chip vendor) and are intentionally not trying to provide CPU load
> metrics. (I think netperf provides both.)  A feature we are adding is to
> warn when we think something other than the socket reads() and writes()
> have become bottlenecks, e.g. in a CPU constrained system it becomes an
> "entangled metric" between i/o and CPU though still presents in network i/o
> units which can be misleading to network device vendors.
> Also, many might want to consider monitoring "network power" which is
> average throughput / latency or delay, i.e. "something good" / "something
> bad"

It's more socket-level statistics I'm after for Flent use; we generally
run multiple instances (flows) concurrently and graph the results. This
is the variables we currently extract from Netperf:

                  'LOCAL_SEND_SIZE,LOCAL_RECV_SIZE,' \
                  'REMOTE_SEND_SIZE,REMOTE_RECV_SIZE,' \

Some of these can be set as well (such as TOS and congestion control

Also, how safe is it to run an iperf server instance on the public
internet? :)


More information about the Make-wifi-fast mailing list