ofs | hex dump | ascii |
---|
0000 | 89 50 4e 47 0d 0a 1a 0a 00 00 00 0d 49 48 44 52 00 00 06 a2 00 00 02 80 08 06 00 00 00 f7 bc 69 | .PNG........IHDR...............i |
0020 | 4c 00 00 0c 15 69 43 43 50 49 43 43 20 50 72 6f 66 69 6c 65 00 00 48 89 95 57 07 54 53 49 17 9e | L....iCCPICC.Profile..H..W.TSI.. |
0040 | 57 52 08 09 2d 10 e9 84 de 91 5e a5 77 a9 d2 c1 46 48 02 84 12 42 20 a8 d8 d1 45 05 d7 2e 2a 58 | WR..-.....^.w...FH...B....E...*X |
0060 | d1 55 11 15 d7 02 c8 5a 11 c5 8a 60 ef 1b 44 54 56 d6 c5 82 0d 95 7f 52 40 d7 fd cb f9 ef 39 f3 | .U.....Z...`..DTV......R@.....9. |
0080 | e6 7b 77 ee bd f3 dd fb 66 de 99 01 40 d9 99 25 10 e4 a1 2a 00 e4 f3 8b 85 71 a1 01 cc 94 d4 34 | .{w.....f...@..%...*.....q.....4 |
00a0 | 26 49 0c 10 40 00 64 60 03 74 58 ec 22 81 7f 6c 6c 24 80 32 d2 ff 5d de dd 82 d6 50 ae db 4a 62 | &I..@.d`.tX."..ll$.2..]....P..Jb |
00c0 | fd 73 fc bf 8a 2a 87 5b c4 06 00 89 85 38 83 53 c4 ce 87 f8 30 00 b8 36 5b 20 2c 06 80 d0 09 f5 | .s...*.[.....8.S....0..6[.,..... |
00e0 | c6 d3 8a 05 12 fc 16 62 75 21 24 08 00 91 2c c1 59 32 ac 2b c1 19 32 6c 2f b5 49 88 0b 84 38 08 | .......bu!$...,.Y2.+..2l/.I...8. |
0100 | 00 32 95 c5 12 66 01 a0 24 89 cf 2c 61 67 c1 38 4a 02 88 ed f9 1c 1e 1f e2 ad 10 fb b0 b3 59 1c | .2...f..$..,ag.8J.............Y. |
0120 | 88 c5 10 db e4 e7 17 40 ac 4c 85 d8 22 e3 bb 38 59 7f 8b 99 31 1a 93 c5 ca 1a c5 b2 5c a4 42 0e | .......@.L.."..8Y...1.......\.B. |
0140 | e2 15 09 f2 58 33 fe cf 72 fc 6f c9 cf 13 8d cc 61 04 1b 35 5b 18 16 27 c9 19 d6 6d 77 6e 41 84 | ....X3..r.o.....a..5[..'...mwnA. |
0160 | 04 43 ee c8 31 7e 46 74 0c c4 6a 10 9f e7 71 a4 f6 12 7c 2f 5b 14 96 28 b7 ef 67 17 05 c2 9a 01 | .C..1~Ft..j...q...|/[..(..g..... |
0180 | 06 00 28 e0 b0 82 22 20 86 b5 44 19 a2 dc 44 7f 39 76 64 09 a5 be d0 1e 8d e6 15 87 27 c8 71 86 | ..(..."...D...D.9vd.........'.q. |
01a0 | b0 20 4e 1e 1f 2d e1 e7 45 47 ca e3 2c ce e6 86 8f e0 cd dc a2 e0 f8 11 9b 4c 5e 48 38 c4 70 a5 | ..N..-..EG..,............L^H8.p. |
01c0 | a1 87 4b b3 13 92 65 3c d1 b6 12 5e 52 34 c4 4a 10 77 16 e5 c6 47 c8 7d 1f 95 66 07 46 8f d8 08 | ..K...e<...^R4.J.w...G.}..f.F... |
01e0 | 45 71 12 ce 26 10 bf cd 14 86 c4 c9 6c 30 cd fc a2 91 bc 30 3b 36 4b 3a 97 26 c4 7e c5 d9 09 61 | Eq..&.......l0.....0;6K:.&.~...a |
0200 | 32 5f 2c 85 5b 94 12 39 c2 81 c3 0d 0a 96 71 c0 38 5c 7e a2 9c 1b 06 57 57 40 9c dc b7 5c 90 17 | 2_,.[..9......q.8\~....WW@...\.. |
0220 | 2b b7 c7 36 73 f3 42 e3 64 75 c6 0e 14 95 c4 8f f8 5e 2b 86 0b 4c 56 07 ec 71 0e 6b 7c ac 8c 3f | +..6s.B.du.......^+..LV..q.k|..? |
0240 | f6 4.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, Ericsson AB and others.
*************************************
Yardstick Test Case Description TC012
*************************************
.. _bw_mem: http://manpages.ubuntu.com/manpages/trusty/bw_mem.8.html
+-----------------------------------------------------------------------------+
|Memory Bandwidth |
| |
+--------------+--------------------------------------------------------------+
|test case id | OPNFV_YARDSTICK_TC012_MEMORY BANDWIDTH |
| | |
+--------------+--------------------------------------------------------------+
|metric | Memory read/write bandwidth (MBps) |
| | |
+--------------+--------------------------------------------------------------+
|test purpose | The purpose of TC012 is to evaluate the IaaS compute |
| | performance with regards to memory throughput. |
| | It measures the rate at which data can be read from and |
| | written to the memory (this includes all levels of memory). |
| | |
| | The purpose is also to be able to spot the trends. |
| | Test results, graphs and similar shall be stored for |
| | comparison reasons and product evolution understanding |
| | between different OPNFV versions and/or configurations. |
| | |
+--------------+--------------------------------------------------------------+
|test tool | LMbench |
| | |
| | LMbench is a suite of operating system microbenchmarks. |
| | This test uses bw_mem tool from that suite including: |
| | * Cached file read |
| | * Memory copy (bcopy) |
| | * Memory read |
| | * Memory write |
| | * Pipe |
| | * TCP |
| | |
| | (LMbench is not always part of a Linux distribution, hence |
| | it needs to be installed. As an example see the |
| | /yardstick/tools/ directory for how to generate a Linux |
| | image with LMbench included.) |
| | |
+--------------+--------------------------------------------------------------+
|test | LMbench bw_mem benchmark allocates twice the specified |
|description | amount of memory, zeros it, and then times the copying of |
| | the first half to the second half. The benchmark is invoked |
| | in a host VM on a compute blade. Results are reported in |
| | megabytes moved per second. |
| | |
+--------------+--------------------------------------------------------------+
|configuration | File: opnfv_yardstick_tc012.yaml |
| | |
| | * SLA (optional): 15000 (MBps) min_bw: The minimum amount of |
| | memory bandwidth that is accepted. |
| | * Size: 10 240 kB - test allocates twice that size |
| | (20 480kB) zeros it and then measures the time it takes to |
| | copy from one side to another. |
| | * Benchmark: rdwr - measures the time to read data into |
| | memory and then write data to the same location. |
| | * Warmup: 0 - the number of iterations to perform before |
| | taking actual measurements. |
| | * Iterations: 10 - test is run 10 times iteratively. |
| | * Interval: 1 - there is 1 second delay between each |
| | iteration. |
| | |
| | SLA is optional. The SLA in this test case serves as an |
| | example. Considerably higher bandwidth is expected. |
| | However, to cover most configurations, both baremetal and |
| | fully virtualized ones, this value should be possible to |
| | achieve and acceptable for black box testing. |
| | Many heavy IO applications start to suffer badly if the |
| | read/write bandwidths are lower than this. |
| | |
+--------------+--------------------------------------------------------------+
|applicability | Test can be configured with different: |
| | |
| | * memory sizes; |
| | * memory operations (such as rd, wr, rdwr, cp, frd, fwr, |
| | fcp, bzero, bcopy); |
| | * number of warmup iterations; |
| | * iterations and intervals. |
| | |
| | Default values exist. |
| | |
| | SLA (optional) : min_bandwidth: The minimun memory bandwidth |
| | that is accepted. |
| | |
+--------------+--------------------------------------------------------------+
|usability | This test case is one of Yardstick's generic test. Thus it |
| | is runnable on most of the scenarios. |
| | |
+--------------+--------------------------------------------------------------+
|references | LMbench bw_mem_ |
| | |
| | ETSI-NFV-TST001 |
| | |
+--------------+--------------------------------------------------------------+
|pre-test | The test case image needs to be installed into Glance |
|conditions | with Lmbench included in the image. |
| | |
| | No POD specific requirements have been identified. |
| | |
+--------------+--------------------------------------------------------------+
|test sequence | description and expected result |
| | |
+--------------+--------------------------------------------------------------+
|step 1 | A host VM with LMbench installed is booted. |
| | |
+--------------+--------------------------------------------------------------+
|step 2 | Yardstick is connected with the host VM by using ssh. |
| | "lmbench_bandwidth_benchmark" bash script is copied from |
| | Jump Host to the host VM via ssh tunnel. |
| | |
+--------------+--------------------------------------------------------------+
|step 3 | 'lmbench_bandwidth_benchmark' script is invoked. LMbench's |
| | bw_mem benchmark starts to measures memory read/write |
| | bandwidth. Memory read/write bandwidth results are recorded |
| | and checked against the SLA. Logs are produced and stored. |
| | |
| | Result: Logs are stored. |
| | |
+--------------+--------------------------------------------------------------+
|step 4 | The host VM is deleted. |
| | |
+--------------+--------------------------------------------------------------+
|test verdict | Test fails if the measured memory bandwidth is below the SLA |
| | value or if there is a test case execution problem. |
| | |
+--------------+--------------------------------------------------------------+
|