8.9 Discussion TBD 8.10 Reporting Format Ideally, the results of testing to assess Throughput or Capacity with X% Loss should be presented using a Figure with a two-dimensional graph. The title of the graph shall include the metric name(s) and the Units of the y-axis (such as Throughput in Frames per second). The Units of the x-axis shall be Frame Size in octets. The Units of the y-axis shall be Frames per second. If the test traffic is bi-directional, then the sum of both traffic directions shall be plotted on the graph for each frame size tested. The y-axis may also present the corresponding bits per second scale, as an option. For tests with variable Frame size [RFC6985], the results shall be plotted according to the average Frame size of the traffic stream (which includes the factors of Frame frequency and Frame size). Along with the measured Frames per second for each Frame size, the Maximum theoretical Frames per second shall be plotted for each Frame size (for simple comparison purposes. The caption of the Figure shall describe all relevant aspects of the test, in sufficient detail to inform a reader and to distinguish each Figure from similar Figures with results from different test conditions conducted as part of the same campaign (such as different test set-ups and protocols used). There shall also be a legend, identifying the benchmark and any other metric-variants plotted. If the graphical results are summarized as a single number, then the result of metric assessment for the smallest Frame size shall be reported, with Units of measure. If the results are summarized in a table, then the example Table below should be used. Trial 8.10-1: Example Throughput Tabular Reporting Requirement Metric Name Frame Size, octets number 64 256 IMIX 1518 Throughput-01 Throughput Capacity with X% Loss The example above assumes IPv4 addresses, and IPv6 addresses would increase the frame size (64 octets becomes 84 octets). 9 Latency 9.1 Background Latency is another key Benchmark for the NFVI. It is valuable to assess the one-way frame transfer time of a SUT at various levels of offered load. This information can assist capacity planning and network engineering when conducted under circumstances relevant to the production network of interest.
8.9 Discussion TBD 8.10 Reporting Format Ideally, the results of testing to assess Throughput or Capacity with X% Loss should be presented using a Figure with a two-dimensional graph. The title of the graph shall include the metric name(s) and the Units of the y-axis (such as Throughput in Frames per second). The Units of the x-axis shall be Frame Size in octets. The Units of the y-axis shall be Frames per second. If the test traffic is bi-directional, then the sum of both traffic directions shall be plotted on the graph for each frame size tested. The y-axis may also present the corresponding bits per second scale, as an option. For tests with variable Frame size [RFC6985], the results shall be plotted according to the average Frame size of the traffic stream (which includes the factors of Frame frequency and Frame size). Along with the measured Frames per second for each Frame size, the Maximum theoretical Frames per second shall be plotted for each Frame size (for simple comparison purposes. The caption of the Figure shall describe all relevant aspects of the test, in sufficient detail to inform a reader and to distinguish each Figure from similar Figures with results from different test conditions conducted as part of the same campaign (such as different test set-ups and protocols used). There shall also be a legend, identifying the benchmark and any other metric-variants plotted. If the graphical results are summarized as a single number, then the result of metric assessment for the smallest Frame size shall be reported, with Units of measure. If the results are summarized in a table, then the example Table below should be used. 8.10-1: Example Throughput Tabular Reporting Requirement number Metric Name Frame Size, octets 64 256 IMIX 1518 Throughput-01 Throughput Capacity with X% Loss The example above assumes IPv4 addresses, and IPv6 addresses would increase the frame size (64 octets becomes 84 octets). 9 Latency 9.1 Background Latency is another key Benchmark for the NFVI. It is valuable to assess the one-way frame transfer time of a SUT at various levels of offered load. This information can assist capacity planning and network engineering when conducted under circumstances relevant to the production network of interest. Trial
NFV-TST009v0011.docx