Code Review / yardstick.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: f37d291) | patch
Extend lmbench scenario to measure memory bandwidth 23/2623/3
authorKristian Hunt <kristian.hunt@gmail.com>
Tue, 13 Oct 2015 14:38:56 +0000 (16:38 +0200)
committerKristian Hunt <kristian.hunt@gmail.com>
Wed, 28 Oct 2015 10:38:48 +0000 (11:38 +0100)
commit05d5ac8d6d5e9bd1e6b69afbd764000aeb4a030e
tree2937a8372d4e672f4d8f755950e9e58779cbdc4btree | snapshot
parentf37d291f6397891cd0dc37c6140b114868921b61commit | diff
Extend lmbench scenario to measure memory bandwidth

Lmbench scenario has now two scripts and will choose between them,
based on whether the intention is to run memory latency or bandwidth
tests. Added also unit test file for this scenario.

JIRA: YARDSTICK-113

Change-Id: I2ba4dbef31f3cafbdb3c583ece5ed9512a906896
Signed-off-by: Kristian Hunt <kristian.hunt@gmail.com>
samples/lmbench.yaml diff | blob | history
tests/functional/test_cli_scenario.py diff | blob | history
tests/unit/benchmark/scenarios/compute/test_lmbench.py [new file with mode: 0644] blob
yardstick/benchmark/scenarios/compute/lmbench.py diff | blob | history
yardstick/benchmark/scenarios/compute/lmbench_bandwidth_benchmark.bash [new file with mode: 0644] blob
yardstick/benchmark/scenarios/compute/lmbench_latency_benchmark.bash [moved from yardstick/benchmark/scenarios/compute/lmbench_benchmark.bash with 100% similarity] blob | history