summaryrefslogtreecommitdiffstats
path: root/samples/lmbench.yaml
diff options
context:
space:
mode:
authorKristian Hunt <kristian.hunt@gmail.com>2015-10-13 16:38:56 +0200
committerKristian Hunt <kristian.hunt@gmail.com>2015-10-28 11:38:48 +0100
commit05d5ac8d6d5e9bd1e6b69afbd764000aeb4a030e (patch)
tree2937a8372d4e672f4d8f755950e9e58779cbdc4b /samples/lmbench.yaml
parentf37d291f6397891cd0dc37c6140b114868921b61 (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>
Diffstat (limited to 'samples/lmbench.yaml')
-rw-r--r--samples/lmbench.yaml21
1 files changed, 20 insertions, 1 deletions
diff --git a/samples/lmbench.yaml b/samples/lmbench.yaml
index 256d8c67e..2b8e99084 100644
--- a/samples/lmbench.yaml
+++ b/samples/lmbench.yaml
@@ -1,6 +1,6 @@
---
# Sample benchmark task config file
-# measure memory read latency using lmbench
+# measure memory read latency and memory bandwidth using lmbench
schema: "yardstick:task:0.1"
@@ -8,6 +8,7 @@ scenarios:
-
type: Lmbench
options:
+ test_type: "latency"
stride: 64
stop_size: 32
@@ -22,6 +23,24 @@ scenarios:
sla:
max_latency: 35
action: monitor
+-
+ type: Lmbench
+ options:
+ test_type: "bandwidth"
+ size: 500
+ benchmark: "wr"
+
+ host: demeter.demo
+
+ runner:
+ type: Arithmetic
+ name: size
+ stop: 2000
+ step: 500
+
+ sla:
+ min_bandwidth: 10000
+ action: monitor
context:
name: demo