1STRESSAPPTEST(1) General Commands Manual STRESSAPPTEST(1)
2
6 stressapptest - stress test application for simulating high load situa‐
7 tions
8
10 stressapptest [options]
11
13 This manual page documents briefly the stressapptest command.
14 stressapptest (unix name for Stressful Application Test) is a program
16 that tries to maximize randomized traffic to memory from processor and
17 I/O, with the intent of creating a realistic high load situation in or‐
18 der to test the existing hardware devices in a computer.
19
21 This program supports the following options:
22 -A Run in degraded mode on incompatible systems.
25 -C <threads>
28 Number of memory CPU stress threads to run.
29 -d <device>
32 Add a direct write disk thread with block device (or file) 'de‐
33 vice'.
34 -f <filename>
37 Add a disk thread with tempfile 'filename'.
38 -F Don't result check each transaction.
41 -i <threads>
44 Number of memory invert threads to run.
45 -l <logfile>
48 Log output to file 'logfile'.
49 -m <threads>
52 Number of memory copy threads to run.
53 -M <mbytes>
56 Megabytes of RAM to test.
57 -n <ipaddr>
60 Add a network thread connecting to system at 'ipaddr'.
61 -p <pagesize>
64 Size in bytes of memory chunks.
65 -s <seconds>
68 Number of seconds to run.
69 -v <level>
72 Verbosity (0-20), default is 8.
73 -W Use more CPU-stressful memory copy.
76 --blocks-per-segment <number>
79 Number of blocks to read/write per segment per iteration (-d).
80 --cache-size <size>
83 Size of disk cache (-d).
84 --cc_inc_count <number>
87 Number of times to increment the cacheline's member.
88 --cc_line_count <number>
91 Number of cache line sized datastructures to allocate for the
92 cache coherency threads to operate.
93 --cc_line_size <number>
96 Size of cache line to use as the basis for cache coherency test
97 data structures.
98 --cc_test
101 Do the cache coherency testing.
102 --destructive
105 Write/wipe disk partition (-d).
106 --filesize <size>
109 Size of disk IO tempfiles.
110 --findfiles
113 Find locations to do disk IO automatically.
114 --force_errors
117 Inject false errors to test error handling.
118 --force_errors_like_crazy
121 Inject a lot of false errors to test error handling.
122 --listen
125 Run threads that listen for incoming net connections.
126 --local_numa
129 Choose memory regions associated with each CPU to be tested by
130 that CPU.
131 --max_errors <number>
134 Exit early after finding specified number of errors.
135 --monitor_mode
138 Only do ECC error polling, no stress load.
139 --no_errors
142 Run without checking for ECC or other errors.
143 --paddr_base <address>
146 Allocate memory starting from this address.
147 --pause_delay <seconds>
150 Delay (in seconds) between power spikes.
151 --pause_duration <seconds>
154 Duration (in seconds) of each pause.
155 --random-threads <number>
158 Number of random threads for each disk write thread (-d).
159 --read-block-size <size>
162 Size of block for reading (-d).
163 --read-threshold <time>
166 Maximum time (in us) a block read should take (-d).
167 --remote_numa <time>
170 Choose memory regions not associated with each CPU to be tested
171 by that CPU.
172 --segment-size <size>
175 Size of segments to split disk into (-d).
176 --stop_on_errors
179 Stop after finding the first error.
180 --write-block-size <size>
183 Size of block for writing (-d). If not defined, the size of
184 block for writing will be defined as the size of block for read‐
185 ing.
186 --write-threshold <time>
189 Maximum time (in us) a block write should take (-d).
190
193 http://code.google.com/p/stressapptest/
194
196 stressapptest was written by Nick Sanders and Rapahel Menderico (Google
197 Inc).
198 This manual page was written by Michael Prokop <mika@debian.org> for
200 the Debian project (and may be used by others).
201 2009-10-20 STRESSAPPTEST(1)