flowgrind  0.8.2
About: Flowgrind is a network performance measurement tool (similar to iperf or netperf).
  Fossies Dox: flowgrind-0.8.2.tar.bz2  ("unofficial" and yet experimental doxygen-generated source code documentation)  

flowgrind Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies flowgrind-0.8.2.tar.bz2 contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).

Flowgrind - TCP traffic generator

Build Status Coverity Scan Build Status

Flowgrind is an advanced TCP traffic generator for testing and benchmarking Linux, FreeBSD, and Mac OS X TCP/IP stacks. In contrast to similar tools like iperf or netperf it features a distributed architecture, where throughput and other metrics are measured between arbitrary flowgrind server processes.

What It Can Do?

Flowgrind measures besides goodput (throughput), the application layer interarrival time (IAT) and round-trip time (RTT), blockcount and network transactions/s. Unlike most cross-platform testing tools, flowgrind can output some transport layer information, which are usually internal to the TCP/IP stack. For example, on Linux and FreeBSD this includes among others the kernel's estimation of the end-to-end RTT, the size of the TCP congestion window (CWND) and slow start threshold (SSTHRESH).

Flowgrind has a distributed architecture. It is split into two components: the flowgrind daemon and the flowgrind controller. Using the controller, flows between any two systems running the flowgrind daemon can be setup (third party tests). At regular intervals during the test the controller collects and displays the measured results from the daemons. It can run multiple flows at once with the same or different settings and individually schedule every one. Test and control connection can optionally be diverted to different interfaces.

The traffic generation itself is either bulk transfer, rate-limited, or sophisticated request/response tests. Flowgrind uses libpcap to automatically dump traffic for qualitative analysis.

Building flowgrind

Flowgrind builds cleanly on Linux, FreeBSD, and Mac OS X. Other operating systems are currently not planned to be supported. Flowgrind expects libxmlrpc-c and OSSP uuid to be available. Additionally, for the optional advanced traffic generation and automatic dump support libgsl an libpcap should be installed.

Flowgrind is built using GNU autotools on all supported platforms. You can build it using the following commands:

# cd flowgrind
# autoreconf -i
# ./configure
# make

For more information see INSTALL.md.

Instructions to run a test

  1. Start flowgrindd on all machines that should be the endpoint of a flow.
  2. Execute flowgrind on some machine (not necessarily one of the endpoints) with the host names of the endpoints passed through the -H option.

Assume we have 4 machines, host0, host1, host2 and host3 and flowgrind has been installed on all of them. We want to measure flows from host1 to host2 and from host1 to host3 in parallel, controlled from host0. First, we start flowgrindd on host1 to host3. On host0 we execute:

# flowgrind -n 2 -F 0 -H s=host1,d=host2 -F 1 -H s=host1,d=host3

In order to not influence the test connection with control traffic, flowgrind allows to setup the RPC control connection over a different interface. A typical scenario would be to test a WiFi connection and run the control traffic over a wired connection.

Assume two machines running flowgrindd, each having two network adapters, one wired, one wireless. We run flowgrind on a machine that is connected by wire to the test machines. First machine has addresses and, the other has addresses and So our host argument will be this:

# flowgrind -H s=,d=

In words: test from to on the nodes identified by and respectively.

See also

There are other popular TCP measurement tools you might look into, especially if you are mainly interested in fast unidirectional bulk transfer performance.

  • Iperf3 - fresh reimplementation of the original iperf
  • Netperf - network performance benchmark, also supports unix domain sockets