To update cyclictest latency threshold values

[kvmfornfv.git] / tests / kvmfornfv_cyclictest_hostenv_guestenv.yaml

diff --git a/tests/kvmfornfv_cyclictest_hostenv_guestenv.yaml b/tests/kvmfornfv_cyclictest_hostenv_guestenv.yaml
index 99c474c..f716c8a 100644 (file)
--- a/tests/kvmfornfv_cyclictest_hostenv_guestenv.yaml
+++ b/tests/kvmfornfv_cyclictest_hostenv_guestenv.yaml
@@ -5,7 +5,7 @@
 # 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 -b 1200000 -i 1000 -p 99 -l 1000 -t 1 -h 90 -m -n -q
+# sudo bash cyclictest -a 1 -b 1000 -i 1000 -p 99 -l 1000 -t 1 -h 90 -m -n -q
 #
 
 schema: "yardstick:task:0.1"
@@ -15,7 +15,7 @@ scenarios:
   type: Cyclictest
   options:
     affinity: 1
-    breaktrace: 1200000
+    breaktrace: 1000
     interval: 1000
     priority: 99
     loops: 600000
@@ -28,9 +28,9 @@ scenarios:
     interval: 1
   tc: "kvmfornfv_cyclictest-node-context"
   sla:
-    max_min_latency: 100
-    max_avg_latency: 600000
-    max_max_latency: 1200000
+    max_min_latency: 50
+    max_avg_latency: 100
+    max_max_latency: 1000
     action: monitor
   setup_options:
     rpm_dir: "/opt/rpm"