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
Next revision
Previous revision
openbach:exploitation:reference_scenarios:network:rate:index [2019/04/15 17:10]
dpradas
openbach:exploitation:reference_scenarios:network:rate:index [2020/01/20 11:39] (current)
kuhnn
Line 3: Line 3:
  
 ==== Context ==== ==== Context ====
-To assess the throughput/​rate in a deployed network, we can exploit different ways of computing the available link rate. Following RFC recommendations (e.g.: RFC 5136 "​Defining Network Capacity, RFC 3148 "A Framework for Defining Empirical Bulk Transfer Capacity Metrics"​ or RFC "6349 "​Framework for TCP Throughput Testing"​),​ we have detailed in [[openbach:​exploitation:​scenarios:​rate:​rfc|RFC ideas]] some interesting items regarding the ways to evaluate the network capacity.+To assess the throughput/​rate in a deployed network, we can exploit different ways of computing the available link rate. Following RFC recommendations (e.g.: RFC 5136 "​Defining Network Capacity, RFC 3148 "A Framework for Defining Empirical Bulk Transfer Capacity Metrics"​ or RFC "6349 "​Framework for TCP Throughput Testing"​),​ we have detailed in [[openbach:​exploitation:​reference_scenarios:​network:​rate:​rfc|RFC ideas]] some interesting items regarding the ways to evaluate the network capacity.
  
 We summarise below some of the specifications:​ We summarise below some of the specifications:​
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 25: Line 26:
 Regarding the rate metrology, it is also possible to perform passive test with jobs that measure the rate of the traffic generated by other components/​jobs,​ such as the [[https://​wiki.net4sat.org/​doku.php?​id=openbach:​exploitation:​jobs:​core_jobs:​ratemonitoring_1.0 |rate monitoring]] job (based on iptables packets/​bits counting). It is recommended to do that for validation purposes, if you are not confident with the metrics shown by iperf3/​nuttcp/​iperf2. Regarding the rate metrology, it is also possible to perform passive test with jobs that measure the rate of the traffic generated by other components/​jobs,​ such as the [[https://​wiki.net4sat.org/​doku.php?​id=openbach:​exploitation:​jobs:​core_jobs:​ratemonitoring_1.0 |rate monitoring]] job (based on iptables packets/​bits counting). It is recommended to do that for validation purposes, if you are not confident with the metrics shown by iperf3/​nuttcp/​iperf2.
  
-We have prepared ​two sets of scenarios:​ +We have prepared ​a OpenBACH reference scenario for the rate metrology:
- +
-  * [[openbach:​exploitation:​scenarios:​rate:network_rate|network_rate]] in TCP mode comparing active measurement jobs (iperf3 and nuttcp). Allowing to compare different parameters (MTU size, ToS, number of parallel flows) on TCP mode, with a post-processing phase allowing to plot timeseries of the Throughput results per test and the CDF. +
- +
  
-  * [[openbach:​exploitation:​scenarios:rate:simple_scenario|Simple scenario]] in UDP/TCP mode comparing active ​and passive measurement jobs +  * [[openbach:​exploitation:​reference_scenarios:​network:rate:network_rate|network_rate]] that launches iperf3/nuttcp in TCP mode and nuttcp in UDP modeThe 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:​scenarios:​rate:​complex_scenario|Complex ​scenario]] with iperf3 and nuttcp: allowing ​to compare ​different parameters ​(MTU size, ToS, number of parallel flows) ​on UDP/TCP mode, with different number of iterations per test and with a post-processing phase allowing to plot timeseries of the Throughput results per test and the CDF. +
-  * [[openbach:​exploitation:​scenarios:​rate:​complex_scenario_dev|Complex scenario OLD dev]] with iperf3 and nuttcp: allowing to compare different parameters ​(MTU size, ToS, number of parallel flows) ​on UDP/TCP modewith different number of iterations per test and with a post-processing phase allowing to plot timeseries of the Throughput results per test and the CDF+
-  * [[openbach:​exploitation:​scenarios:​rate:​new_scenario_dev|Scenario version dev 2.x]] test to perform an UDP rate test to measure the network conditions by means of nuttcp.+
  
 +==== 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.1555341046.txt.gz · Last modified: 2019/06/11 16:18 (external edit)