diff options
| author |   Kristian Hunt <kristian.hunt@gmail.com> | 2015-12-10 14:35:59 +0100 |
|---|---|---|
| committer |   Jörgen Karlsson <jorgen.w.karlsson@ericsson.com> | 2015-12-21 23:25:46 +0000 |
| commit | 52d1b3111f37a6b8bc2b6a18e3443dc29fcb943b (patch) | |
| tree | 368a739f98931b641ecb7b68afbd19623d3ee417 /docs | |
| parent | 804abc1206a1ca23d1d1eca0b63b54abca850a26 (diff) | |
Add test case description and task file for TC010
Add test case description for Memory Latency (TC010) and test case
.yaml task file.
JIRA: YARDSTICK-94
Change-Id: If7fb120868c9901fe097f310aa249e1fbc8a94ee
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/yardstick/opnfv_yardstick_tc010.rst | 65 |
1 files changed, 65 insertions, 0 deletions
diff --git a/docs/yardstick/opnfv_yardstick_tc010.rst b/docs/yardstick/opnfv_yardstick_tc010.rst new file mode 100644 index 000000000..c2f8eb4e2 --- /dev/null +++ b/docs/yardstick/opnfv_yardstick_tc010.rst @@ -0,0 +1,65 @@ + +************************************* +Yardstick Test Case Description TC010 +************************************* ++-----------------------------------------------------------------------------+ +|Memory Latency | ++==============+==============================================================+ +|test case id | OPNFV_YARDSTICK_TC010_Memory Latency | ++--------------+--------------------------------------------------------------+ +|metric | Latency in nanoseconds | ++--------------+--------------------------------------------------------------+ +|test purpose | Measure the memory read latency for varying memory sizes and | +| | strides. Whole memory hierarchy is measured including all | +| | levels of cache. | ++--------------+--------------------------------------------------------------+ +|configuration | File: opnfv_yardstick_tc010.yaml | +| | | +| | * SLA (max_latency): 30 nanoseconds | +| | * Stride - 128 bytes | +| | * Stop size - 64 megabytes | +| | * Iterations: 10 - test is run 10 times iteratively. | +| | * Interval: 1 - there is 1 second delay between each | +| | iteration. | ++--------------+--------------------------------------------------------------+ +|test tool | Lmbench | +| | | +| | Lmbench is a suite of operating system microbenchmarks. This | +| | test uses lat_mem_rd tool from that suite. | +| | Lmbench is not always part of a Linux distribution, hence it | +| | needs to be installed in the test image | +| | (See :ref:`guest-image` for how to generate a Linux image | +| | for Glance with Lmbench included). | ++--------------+--------------------------------------------------------------+ +|references |* http://manpages.ubuntu.com/manpages/trusty/lat_mem_rd.8.html| +| | | +| |* McVoy, Larry W., and Carl Staelin. "lmbench: Portable Tools | +| | for Performance Analysis." *USENIX annual technical | +| | conference*. 1996. | ++--------------+--------------------------------------------------------------+ +|applicability | Test can be configured with different | +| | * strides; | +| | * stop_size; | +| | * iterations and intervals; | +| | | +| | There are default values for each above-mentioned option. | +| | | +| | * SLA (optional). | +| | max_latency: The maximum memory latency that is | +| | accepted. | ++--------------+--------------------------------------------------------------+ +|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 | step | description | result | +| +------+----------------------------------+--------------------+ +| | 1 | The host is installed as client. | Logs are stored | +| | | Lmbench's lat_mem_rd tool is | | +| | | invoked and logs are produced and| | +| | | stored. | | ++--------------+------+----------------------------------+--------------------+ +|test verdict | Test fails if the measured memory latency is above the SLA | +| | value or if there is a test case execution problem. | ++--------------+--------------------------------------------------------------+ |