Flowgrind

  1. Bug #1239988
  2. Comment #1

Comment 1 for bug 1239988

Revision history for this message
Alexander Zimmermann (alexander-zimmermann) wrote :

You need to increase the bock/message/IO size to saturate a 10 Gb/s link:

alexandz@six:~$ flowgrind -H s=240.0.20.1/192.168.10.1,d=240.0.20.2/192.168.11.1 -Q -S s=65536
# Fri Nov 29 19:17:18 2013: controlling host = six, number of flows = 1, reporting interval = 0.05s, [through] = 10**6 bit/second (flowgrind-0.6.1-48-g6451ca)

# 0 S: 240.0.20.1/192.168.10.1 (Linux 3.12.0phobos+), random seed: 2625273754, sbuf = 16384/0, rbuf = 87380/0 (real/req), SMSS = 1448, Path MTU = 1500, Interface MTU = 1500 (Ethernet/PPP), flow duration = 10.000s/10.000s (real/req), through = 9397.875158/0.000000Mbit/s (out/in), request blocks = 179252/0 (out/in)
# 0 D: 240.0.20.2/192.168.11.1 (Linux 3.12.0phobos+), random seed: 2625273754, sbuf = 16384/0, rbuf = 87380/0 (real/req), SMSS = 1448, Path MTU = 1500, Interface MTU = 1500 (Ethernet/PPP), through = 0.000000/9396.541536Mbit/s (out/in), request blocks = 0/179224 (out/in), IAT = 0.012/0.056/0.806 (min/avg/max)

However, it's right that flowgrind burns more CPU then netsurf. Further investigation is needed.