User Tools

Site Tools


openbach:exploitation:reference_scenarios:network:rate:index

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
openbach:exploitation:reference_scenarios:network:rate:index [2019/06/11 16:21]
127.0.0.1 external edit
openbach:exploitation:reference_scenarios:network:rate:index [2020/01/20 11:39]
kuhnn
Line 18: Line 18:
  
 ==== Objective ==== ==== Objective ====
 +
 We recommend to compare at least two of the following OpenBACH jobs (iperf3 and nuttcp), which are based on active rate measurements (i.e. they perform measurements based on their own generated traffic): We recommend to compare at least two of the following OpenBACH jobs (iperf3 and nuttcp), which are based on active rate measurements (i.e. they perform measurements based on their own generated traffic):
   * ''​iperf3''​ (server or client) generate TCP/UDP traffic and performs different kind of measurements on this traffic. Regarding TCP traffic, it tries to charge the link (depending on the window size) and it is capable of measuring rate (b/s) and data sent (bits). Regarding the UDP traffic, it is possible to specify the bit rate, and it is capable of measuring rate (b/s), data sent (bits), packets sent, jitter (ms), loss and PLR.   * ''​iperf3''​ (server or client) generate TCP/UDP traffic and performs different kind of measurements on this traffic. Regarding TCP traffic, it tries to charge the link (depending on the window size) and it is capable of measuring rate (b/s) and data sent (bits). Regarding the UDP traffic, it is possible to specify the bit rate, and it is capable of measuring rate (b/s), data sent (bits), packets sent, jitter (ms), loss and PLR.
Line 29: Line 30:
   * [[openbach:​exploitation:​reference_scenarios:​network:​rate:​network_rate|network_rate]] that launches iperf3/​nuttcp in TCP mode and nuttcp in UDP mode. The scenario allows to modify different traffic parameters on TCP mode (such as MTU size, ToS, number of parallel flows), with a post-processing phase allowing to plot timeseries of the Throughput results per test and the CDF.   * [[openbach:​exploitation:​reference_scenarios:​network:​rate:​network_rate|network_rate]] that launches iperf3/​nuttcp in TCP mode and nuttcp in UDP mode. The scenario allows to modify different traffic parameters on TCP mode (such as MTU size, ToS, number of parallel flows), with a post-processing phase allowing to plot timeseries of the Throughput results per test and the CDF.
  
 +==== Limitations ====
  
 +The reference scenario associated to the rate metrology is currently limited to estimating a network with 650 ms and 230 Mbps (for iperf3 and nuttcp) in TCP. 
openbach/exploitation/reference_scenarios/network/rate/index.txt · Last modified: 2020/01/20 11:39 by kuhnn