aboutsummaryrefslogtreecommitdiffstats
path: root/samples/cyclictest.yaml
diff options
context:
space:
mode:
authorQiLiang <liangqi1@huawei.com>2015-09-07 21:55:29 +0800
committerQiLiang <liangqi1@huawei.com>2015-10-15 09:59:34 +0800
commitc967d7365e1256a257ceb9880caa02d6942dfad7 (patch)
tree6d49f29db2dbbd15023dfeeafd2e5dee9b68531f /samples/cyclictest.yaml
parent15e8300a8e85d5907c5ea90da505929b8ca85ca0 (diff)
Add Cyclictest scenario and sample
Support measuring operating system's high resolution by using Cyclictest. JIRA: YARDSTICK-122 Change-Id: I2e00ce117e263deaaf52cd2d663b845bd5b65432 Signed-off-by: QiLiang <liangqi1@huawei.com>
Diffstat (limited to 'samples/cyclictest.yaml')
-rw-r--r--samples/cyclictest.yaml44
1 files changed, 44 insertions, 0 deletions
diff --git a/samples/cyclictest.yaml b/samples/cyclictest.yaml
new file mode 100644
index 000000000..6a16bd234
--- /dev/null
+++ b/samples/cyclictest.yaml
@@ -0,0 +1,44 @@
+---
+# Sample benchmark task config file
+# Measure system high resolution by using Cyclictest
+#
+# For this sample just like running the command below on the test vm and
+# getting latencies info back to the yardstick.
+#
+# sudo bash cyclictest -a 1 -i 1000 -p 99 -l 1000 -t 1 -h 90 -m -n -q
+#
+
+schema: "yardstick:task:0.1"
+
+scenarios:
+-
+ type: Cyclictest
+ options:
+ affinity: 1
+ interval: 1000
+ priority: 99
+ loops: 1000
+ threads: 1
+ histogram: 90
+ host: kvm.demo
+ runner:
+ type: Duration
+ duration: 60
+ interval: 1
+ sla:
+ max_min_latency: 50
+ max_avg_latency: 100
+ max_max_latency: 1000
+ action: monitor
+
+context:
+ name: demo
+ image: yardstick-trusty-server
+ flavor: yardstick-flavor
+ user: ec2-user
+ servers:
+ kvm:
+ floating_ip: true
+ networks:
+ test:
+ cidr: "10.0.1.0/24"