1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, Huawei Technologies Co.,Ltd and others.
6 *************************************
7 Yardstick Test Case Description TC071
8 *************************************
10 .. _cirros: https://download.cirros-cloud.net
11 .. _pktgen: https://www.kernel.org/doc/Documentation/networking/pktgen.txt
12 .. _cachestat: https://github.com/brendangregg/perf-tools/tree/master/fs
14 +-----------------------------------------------------------------------------+
15 |Latency, Cache Utilization, Throughput, Packet Loss |
17 +--------------+--------------------------------------------------------------+
18 |test case id | OPNFV_YARDSTICK_TC071_Latency, Cache Utilization, |
19 | | Throughput,Packet Loss |
21 +--------------+--------------------------------------------------------------+
22 |metric | Number of flows, latency, throughput, Cache Utilization, |
25 +--------------+--------------------------------------------------------------+
26 |test purpose | To evaluate the IaaS network performance with regards to |
27 | | flows and throughput, such as if and how different amounts |
28 | | of flows matter for the throughput between hosts on different|
29 | | compute blades. Typically e.g. the performance of a vSwitch |
30 | | depends on the number of flows running through it. Also |
31 | | performance of other equipment or entities can depend |
32 | | on the number of flows or the packet sizes used. |
33 | | The purpose is also to be able to spot trends. |
34 | | Test results, graphs and similar shall be stored for |
35 | | comparison reasons and product evolution understanding |
36 | | between different OPNFV versions and/or configurations. |
38 +--------------+--------------------------------------------------------------+
39 |configuration | file: opnfv_yardstick_tc071.yaml |
41 | | Packet size: 64 bytes |
42 | | Number of ports: 1, 10, 50, 100, 300, 500, 750 and 1000. |
43 | | The amount configured ports map from 2 up to 1001000 flows, |
44 | | respectively. Each port amount is run two times, for 20 |
45 | | seconds each. Then the next port_amount is run, and so on. |
46 | | During the test Cache Utilization on both client and server, |
47 | | and the network latency between the client and server are |
49 | | The client and server are distributed on different HW. |
50 | | For SLA max_ppm is set to 1000. |
52 +--------------+--------------------------------------------------------------+
55 | | Pktgen is not always part of a Linux distribution, hence it |
56 | | needs to be installed. It is part of the Yardstick Glance |
58 | | (As an example see the /yardstick/tools/ directory for how |
59 | | to generate a Linux image with pktgen included.) |
63 | | Ping is normally part of any Linux distribution, hence it |
64 | | doesn't need to be installed. It is also part of the |
65 | | Yardstick Glance image. |
66 | | (For example also a cirros_ image can be downloaded, it |
71 | | cachestat is not always part of a Linux distribution, hence |
72 | | it needs to be installed. |
74 +--------------+--------------------------------------------------------------+
75 |references | Ping man pages |
83 +--------------+--------------------------------------------------------------+
84 |applicability | Test can be configured with different packet sizes, amount |
85 | | of flows and test duration. Default values exist. |
87 | | SLA (optional): max_ppm: The number of packets per million |
88 | | packets sent that are acceptable to lose, not received. |
90 +--------------+--------------------------------------------------------------+
91 |pre-test | The test case image needs to be installed into Glance |
92 |conditions | with pktgen included in it. |
94 | | No POD specific requirements have been identified. |
96 +--------------+--------------------------------------------------------------+
97 |test sequence | description and expected result |
99 +--------------+--------------------------------------------------------------+
100 |step 1 | The hosts are installed, as server and client. pktgen is |
101 | | invoked and logs are produced and stored. |
103 | | Result: Logs are stored. |
105 +--------------+--------------------------------------------------------------+
106 |test verdict | Fails only if SLA is not passed, or if there is a test case |
107 | | execution problem. |
109 +--------------+--------------------------------------------------------------+