diff options
| author |   kubi <jean.gaoliang@huawei.com> | 2016-01-11 22:58:13 +0800 |
|---|---|---|
| committer |   qi liang <liangqi1@huawei.com> | 2016-01-11 15:49:31 +0000 |
| commit | 8bbc0bd8ac3c6060f5b5ee3591bccf61e2aeca86 (patch) | |
| tree | 91a30ee3f3fedea26f7a97a4e6a610e2f72264cf /docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst | |
| parent | 6c0b5d537c4933a1e71a1dd644227d9d48ff3f09 (diff) | |
Test case to measure processing speed(score)
run unixbench to get the score of processing performance
This patch includes the .yaml for the test case and the .rst for test case description.
JIRA:YARDSTICK-116
Signed-off-by: kubi <jean.gaoliang@huawei.com>
Change-Id: Ic75119d1db19dacc57edfa4dce607e0e29ae8db4
Signed-off-by: kubi <jean.gaoliang@huawei.com>
(cherry picked from commit db643f9a2a416c0888931a347488a51264350c8f)
Diffstat (limited to 'docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst')
| -rw-r--r-- | docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst | 69 |
1 files changed, 69 insertions, 0 deletions
diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst new file mode 100644 index 000000000..68d36ecd2 --- /dev/null +++ b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc014.rst @@ -0,0 +1,69 @@ +************************************* +Yardstick Test Case Description TC014 +************************************* + +.. _unixbench: https://github.com/kdlucas/byte-unixbench/blob/master/UnixBench + ++-----------------------------------------------------------------------------+ +|Processing speed | +| | ++--------------+--------------------------------------------------------------+ +|test case id | OPNFV_YARDSTICK_TC014_Processing speed | +| | | ++--------------+--------------------------------------------------------------+ +|metric | score of single cpu running, score of parallel running | +| | | ++--------------+--------------------------------------------------------------+ +|test purpose | To evaluate the IaaS processing speed with regards to score | +| | of single cpu running and parallel running | +| | The purpose is also to be able to spot trends. Test results, | +| | graphs and similar shall be stored for comparison reasons | +| | and product evolution understanding between different OPNFV | +| | versions and/or configurations. | +| | | ++--------------+--------------------------------------------------------------+ +|configuration | file: opnfv_yardstick_tc014.yaml | +| | | +| | run_mode: Run unixbench in quiet mode or verbose mode | +| | test_type: dhry2reg, whetstone and so on | +| | | +| | For SLA with single_score and parallel_score, both can be | +| | set by user, default is NA | +| | | ++--------------+--------------------------------------------------------------+ +|test tool | unixbench | +| | | +| | (unixbench 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 unixbench included.) | +| | | ++--------------+--------------------------------------------------------------+ +|references | unixbench_ | +| | | +| | ETSI-NFV-TST001 | +| | | ++--------------+--------------------------------------------------------------+ +|applicability | Test can be configured with different test types, dhry2reg, | +| | whetstone and so on. | +| | | ++--------------+--------------------------------------------------------------+ +|pre-test | The test case image needs to be installed into Glance | +|conditions | with unixbench included in it. | +| | | +| | No POD specific requirements have been identified. | +| | | ++--------------+--------------------------------------------------------------+ +|test sequence | description and expected result | +| | | ++--------------+--------------------------------------------------------------+ +|step 1 | The hosts are installed, as a client. unixbench is | +| | invoked and logs are produced and stored. | +| | | +| | Result: Logs are stored. | +| | | ++--------------+--------------------------------------------------------------+ +|test verdict | Fails only if SLA is not passed, or if there is a test case | +| | execution problem. | +| | | ++--------------+--------------------------------------------------------------+ |