From 05d5ac8d6d5e9bd1e6b69afbd764000aeb4a030e Mon Sep 17 00:00:00 2001 From: Kristian Hunt Date: Tue, 13 Oct 2015 16:38:56 +0200 Subject: 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 --- samples/lmbench.yaml | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) (limited to 'samples') 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 -- cgit 1.2.3-korg