1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, Ericsson AB and others.
6 *************************************
7 Yardstick Test Case Description TC038
8 *************************************
10 .. _cirros: https://download.cirros-cloud.net
11 .. _pktgen: https://www.kernel.org/doc/Documentation/networking/pktgen.txt
13 +-----------------------------------------------------------------------------+
14 |Latency, CPU Load, Throughput, Packet Loss (Extended measurements) |
16 +--------------+--------------------------------------------------------------+
17 |test case id | OPNFV_YARDSTICK_TC038_Latency,CPU Load,Throughput,Packet Loss|
19 +--------------+--------------------------------------------------------------+
20 |metric | Number of flows, latency, throughput, CPU load, packet loss |
22 +--------------+--------------------------------------------------------------+
23 |test purpose | To evaluate the IaaS network performance with regards to |
24 | | flows and throughput, such as if and how different amounts |
25 | | of flows matter for the throughput between hosts on different|
26 | | compute blades. Typically e.g. the performance of a vSwitch |
27 | | depends on the number of flows running through it. Also |
28 | | performance of other equipment or entities can depend |
29 | | on the number of flows or the packet sizes used. |
30 | | The purpose is also to be able to spot trends. Test results, |
31 | | graphs ans similar shall be stored for comparison reasons and|
32 | | product evolution understanding between different OPNFV |
33 | | versions and/or configurations. |
35 +--------------+--------------------------------------------------------------+
36 |configuration | file: opnfv_yardstick_tc038.yaml |
38 | | Packet size: 64 bytes |
39 | | Number of ports: 1, 10, 50, 100, 300, 500, 750 and 1000. |
40 | | The amount configured ports map from 2 up to 1001000 flows, |
41 | | respectively. Each port amount is run ten times, for 20 |
42 | | seconds each. Then the next port_amount is run, and so on. |
43 | | During the test CPU load on both client and server, and the |
44 | | network latency between the client and server are measured. |
45 | | The client and server are distributed on different HW. |
46 | | For SLA max_ppm is set to 1000. |
48 +--------------+--------------------------------------------------------------+
51 | | (Pktgen is not always part of a Linux distribution, hence it |
52 | | needs to be installed. It is part of the Yardstick Glance |
54 | | As an example see the /yardstick/tools/ directory for how |
55 | | to generate a Linux image with pktgen included.) |
59 | | Ping is normally part of any Linux distribution, hence it |
60 | | doesn't need to be installed. It is also part of the |
61 | | Yardstick Glance image. |
62 | | (For example also a cirros_ image can be downloaded, it |
67 | | (Mpstat is not always part of a Linux distribution, hence it |
68 | | needs to be installed. It is part of the Yardstick Glance |
71 +--------------+--------------------------------------------------------------+
72 |references | Ping and Mpstat man pages |
78 +--------------+--------------------------------------------------------------+
79 |applicability | Test can be configured with different packet sizes, amount |
80 | | of flows and test duration. Default values exist. |
82 | | SLA (optional): max_ppm: The number of packets per million |
83 | | packets sent that are acceptable to loose, not received. |
85 +--------------+--------------------------------------------------------------+
86 |pre-test | The test case image needs to be installed into Glance |
87 |conditions | with pktgen included in it. |
89 | | No POD specific requirements have been identified. |
91 +--------------+--------------------------------------------------------------+
92 |test sequence | description and expected result |
94 +--------------+--------------------------------------------------------------+
95 |step 1 | The hosts are installed, as server and client. pktgen is |
96 | | invoked and logs are produced and stored. |
98 | | Result: Logs are stored. |
100 +--------------+--------------------------------------------------------------+
101 |test verdict | Fails only if SLA is not passed, or if there is a test case |
102 | | execution problem. |
104 +--------------+--------------------------------------------------------------+