1RTEVAL(8) System Manager's Manual RTEVAL(8)
2
3
4
6 rteval - evaluate latency performance of a realtime Linux system
7
9 rteval [ -hvsLSDOZ ] [-d duration ] [-w workdir ] [-l loaddir ] [-X
10 host ]
11
12
13 The rteval program is used to evaluate the realtime performance of a
14 realtime Linux kernel on a particular hardware system. There is nothing
15 that actually requires a realtime Linux kernel, but the latency mea‐
16 surements will usually be pretty bad on a stock Linux kernel.
17
18
19
21 These programs follow the usual GNU command line syntax, with long
22 options starting with two dashes ('--').
23 A summary of options is included below.
24
25 -h, --help
26 print a help message
27
28 -d, --duration=DURATION
29 Specify the length of the measurement run. DURATION is an inte‐
30 ger with an optional suffix indicating the units:
31
32 s - seconds
33 m - minutes
34 h - hours
35 d - days
36 for example to execute a ten minute run of rteval:
37 $ rteval --duration=10m
38
39 -v, --verbose
40 Increase the verbosity of output during the test run
41
42 -w WORKDIR, --workdir=WORKDIR
43 Tell rteval to change directory to WORKDIR before creating any
44 subdirectories for report files. The default WORKDIR is the
45 directory in which rteval was started.
46
47 -l LOADDIR, --loaddir=LOADDIR
48 Tell rteval where to find the source for the loads
49
50 --loads-cpulist=CPULIST
51 List of CPUs where loads will run
52
53 --measurement-cpulist=CPULIST
54 List of CPUs where measurement applciation will run
55
56 -s, --sysreport
57 Have rteval run the sysreport utility after a run to gather
58 information on the running system.
59
60 -D, --debug
61 Turn on debugging prints during run
62
63 -X HOST, --xmprpc-submit=HOST
64 Have rteval send report data to HOST following the run, using
65 XML-RPC
66
67 -P, --xmlrpc-no-abort
68 Do not abort if XML-RPC server do not respond to ping request
69
70 -Z, --summarize
71 Have rteval summarize an existing report. This will not cause
72 loads or meausurement utilities to be run.
73
74 -H, --raw-histogram
75 Generate raw histogram data for an already existing XML report
76
77 -f INIFILE, --inifile=INIFILE
78 Initialization file for configuring loads and behavior
79
80 -a COMMENT, --annotate=COMMENT
81 Add a little annotation which is stored in the report
82
83 -L, --logging
84 Log the output of the loads in the report directory
85
86 -O, --onlyload
87 Only run the loads (don't run measurement threads)
88
89
91 These are options that affect the execution behavior of the measurement
92 and load modules.
93
94 --cyclictest-priority=PRIORITY
95 SCHED_FIFO priority for measurement threads (default: 95)
96
97 --cyclictest-interval=INTERVAL
98 Measurement thread interval in microseconds (default: 100)
99
100 --cyclictest-distance=DISTANCE
101 Interval increment in microseconds (default: 0)
102
103 --cyclictest-buckets=NBUCKETS
104 Number of 1 microsecond histogram buckets (default: 2000)
105
106 --hackbench-jobspercore=N
107 Number of jobs per online-core for hackbench load
108
109 --kcompile-jobspercore=N
110 Number of jobs per online-core for kernel compile load
111
112
114 rteval-YYYYMMDD-S This is a directory created by rteval to hold the
115 summary.xml file as well as other files collected on the system. It is
116 the current Year, Month, and Day, followed by a sequence number for
117 multiple runs on the same day.
118
119 summary.xml This is an XML file that contains information about a test
120 run and the host system upon which rteval was run. dmesg This is the
121 output of the dmesg(1) program immediately following system boot. It is
122 copied from /var/log/dmesg.
123
124
126 cyclictest(8).
127
129 rteval was written by Clark Williams <williams@redhat.com>
130
131 XML-RPC and database code by David Sommerseth <davids@redhat.com>
132
133
134
135 august 27, 2009 RTEVAL(8)