blob: 99c474c000423c0f9fa015688e2ff847c3098482 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
---
# 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 -b 1200000 -i 1000 -p 99 -l 1000 -t 1 -h 90 -m -n -q
#
schema: "yardstick:task:0.1"
scenarios:
-
type: Cyclictest
options:
affinity: 1
breaktrace: 1200000
interval: 1000
priority: 99
loops: 600000
threads: 1
histogram: 90
host: kvm.LF
runner:
type: Duration
duration: 1
interval: 1
tc: "kvmfornfv_cyclictest-node-context"
sla:
max_min_latency: 100
max_avg_latency: 600000
max_max_latency: 1200000
action: monitor
setup_options:
rpm_dir: "/opt/rpm"
script_dir: "/opt/scripts"
image_dir: "/opt/image"
host_setup_seqs:
- "host-setup0.sh"
- "reboot"
- "host-setup1.sh"
- "host-install-qemu.sh"
- "host-run-qemu.sh"
guest_setup_seqs:
- "guest-setup0.sh"
- "reboot"
- "guest-setup1.sh"
context:
type: Node
name: LF
file: /opt/scripts/pod.yaml
env:
type: script
prefix: yardstick.benchmark.scenarios.compute
teardown:
-
kvm:
script: disable_trace.bash
|
