-
Notifications
You must be signed in to change notification settings - Fork 7
/
Copy pathdevice.job
103 lines (90 loc) · 2.79 KB
/
device.job
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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
#
# device class stressors:
# various options have been commented out, one can remove the
# proceeding comment to enable these options if required.
#
# run the following tests in parallel or sequentially
#
run sequential
# run parallel
#
# aggressive:
# enables more file, cache and memory aggressive options. This may
# slow tests down, increase latencies and reduce the number of
# bogo ops as well as changing the balance of user time vs system
# time used depending on the type of stressor being used.
#
# aggressive
#
# ignite-cpu:
# alter kernel controls to try and maximize the CPU. This requires
# root privilege to alter various /sys interface controls. Cur‐
# rently this only works for Intel P-State enabled x86 systems on
# Linux.
#
# ignite-cpu
#
# keep-name:
# by default, stress-ng will attempt to change the name of the
# stress processes according to their functionality; this option
# disables this and keeps the process names to be the name of the
# parent process, that is, stress-ng.
#
# keep-name
#
# metrics-brief:
# enable metrics and only output metrics that are non-zero.
#
metrics-brief
#
# verbose
# show all debug, warnings and normal information output.
#
verbose
#
# run each of the tests for 60 seconds
# stop stress test after N seconds. One can also specify the units
# of time in seconds, minutes, hours, days or years with the suf‐
# fix s, m, h, d or y.
#
timeout 60s
#
# per stressor options start here
#
#
# dev stressor options:
# start N workers that exercise the /dev devices. Each worker runs
# 5 concurrent threads that perform open(2), fstat(2), lseek(2),
# poll(2), fcntl(2), mmap(2), munmap(2), fsync(2) and close(2) on
# each device. Note that watchdog devices are not exercised.
#
dev 0 # 0 means 1 stressor per CPU
# dev-ops 1000000 # stop after 1000000 bogo ops
#
# full stressor options:
# start N workers that exercise /dev/full. This attempts to write
# to the device (which should always get error ENOSPC), to read
# from the device (which should always return a buffer of zeros)
# and to seek randomly on the device (which should always suc‐
# ceed). (Linux only).
#
full 0 # 0 means 1 stressor per CPU
# full-ops 1000000 # stop after 1000000 bogo ops
#
# null stressor options:
# start N workers writing to /dev/null
#
null 0 # 0 means 1 stressor per CPU
# null-ops 1000000 # stop after 1000000 bogo ops
#
# urandom stressor options:
# start N workers reading /dev/urandom (Linux only). This will
# load the kernel random number source.
urandom 0 # 0 means 1 stressor per CPU
# urandom-ops 1000000 # stop after 1000000 bogo ops
#
# zero stressor option:
# start N workers reading /dev/zero
#
zero 0 # 0 means 1 stressor per CPU
zero-ops 1000000 # stop after 1000000 bogo ops