[netperf-talk] simulating a single-connection, bidirectional test with TCP_RR

[Rick Jones]

Folks -

In another forum, there was talk about single-connection, bidirectional tests. 
Presently, netperf does not have a "TCP_BISTREAM" test.  However, if one 
configures netperf with --enable-burst, and are careful about socket buffer 
sizes relative to the request/response sizes and the burst size, one can achieve 
the same thing.  Here, for example are a set of TCP_RR tests, without the burst, 
and then with a burst of 0, 1, 2 and 4 requests:

sweb142:/home/raj/netperf2_work# src/netperf -t TCP_RR  -H 192.168.3.1 -- -s 
128K -S 128K -r 16K
TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.3.1 
(192.168.3.1) port 0 AF_INET
Local /Remote
Socket Size   Request  Resp.   Elapsed  Trans.
Send   Recv   Size     Size    Time     Rate
bytes  Bytes  bytes    bytes   secs.    per sec

262142 262142 16384    16384   10.00    1999.85
131072 131072
sweb142:/home/raj/netperf2_work# src/netperf -t TCP_RR  -H 192.168.3.1 -- -s 
128K -S 128K -r 16K -b 0
TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.3.1 
(192.168.3.1) port 0 AF_INET
Local /Remote
Socket Size   Request  Resp.   Elapsed  Trans.
Send   Recv   Size     Size    Time     Rate
bytes  Bytes  bytes    bytes   secs.    per sec

262142 262142 16384    16384   10.00    1999.46
131072 131072
sweb142:/home/raj/netperf2_work# src/netperf -t TCP_RR  -H 192.168.3.1 -- -s 
128K -S 128K -r 16K -b 1
TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.3.1 
(192.168.3.1) port 0 AF_INET
Local /Remote
Socket Size   Request  Resp.   Elapsed  Trans.
Send   Recv   Size     Size    Time     Rate
bytes  Bytes  bytes    bytes   secs.    per sec

262142 262142 16384    16384   10.00    3998.59
131072 131072
sweb142:/home/raj/netperf2_work# src/netperf -t TCP_RR  -H 192.168.3.1 -- -s 
128K -S 128K -r 16K -b 2
TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.3.1 
(192.168.3.1) port 0 AF_INET
Local /Remote
Socket Size   Request  Resp.   Elapsed  Trans.
Send   Recv   Size     Size    Time     Rate
bytes  Bytes  bytes    bytes   secs.    per sec

262142 262142 16384    16384   10.00    5285.34
131072 131072
sweb142:/home/raj/netperf2_work# src/netperf -t TCP_RR  -H 192.168.3.1 -- -s 
128K -S 128K -r 16K -b 4
TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.3.1 
(192.168.3.1) port 0 AF_INET
Local /Remote
Socket Size   Request  Resp.   Elapsed  Trans.
Send   Recv   Size     Size    Time     Rate
bytes  Bytes  bytes    bytes   secs.    per sec

262142 262142 16384    16384   10.00    6376.51
131072 131072

A bit of math shows that 16384 bytes, 6376.51 times per second is ~836 Mbit/s 
each way.

happy benchmarking,

rick jones