-
Notifications
You must be signed in to change notification settings - Fork 19
Expand file tree
/
Copy patholtpcore.html
More file actions
254 lines (182 loc) · 8.09 KB
/
oltpcore.html
File metadata and controls
254 lines (182 loc) · 8.09 KB
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
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Thu Sep 28 15:49:44 2023 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; vertical-align: top }
pre { margin-top: 0; margin-bottom: 0; vertical-align: top }
table { margin-top: 0; margin-bottom: 0; vertical-align: top }
h1 { text-align: center }
</style>
<title>oltpcore</title>
</head>
<body>
<h1 align="center">oltpcore</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#COMPLETION">COMPLETION</a><br>
<a href="#USAGE">USAGE</a><br>
<a href="#COPYRIGHT">COPYRIGHT</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<h2>NAME
<a name="NAME"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">oltpcore
− Perform one run using the oltp workload</p>
<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>[-H] [-g|-G]
[-a] [-n processes] [-k key] [-r runperiod] [-b] [-R
runfile] [-W] [-K nn] [-p file] [-s file] [-o file] komment
text ...</b></p>
<p style="margin-left:11%; margin-top: 1em">Execute one run
using the oltp workload, saving intermediate results in the
results directory and partially making final results
available in the awr directory for browsing. Note that
stdout and stderr are not saved.</p>
<p style="margin-left:11%; margin-top: 1em">Any arguments
are added as extra komment text using -K option to
rwloadsim; it must be preceded by -- if it includes any text
that appear like options.</p>
<p style="margin-left:11%; margin-top: 1em">Options can be
provided using gnu style long options as shown below. If a
short options takes an argument, so does a long option.</p>
<h2>OPTIONS
<a name="OPTIONS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>-H|--help</b></p>
<p style="margin-left:17%;">Print short help.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-n|--processcount
N</b></p>
<p style="margin-left:17%;">Set the number of processes,
default 1</p>
<p style="margin-left:11%; margin-top: 1em"><b>-k|--key
key</b></p>
<p style="margin-left:17%;">Set the key that will be used
when storing results in the repository database. The default
is the same as the project name.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-r|--runperiod
N</b></p>
<p style="margin-left:17%;">Set the runperiod in seconds;
the default is 295s. You will get the nicest graphs if the
value chosen is a bit less than a multiple of 300s. If less
than 120s, no awr reports will be created.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-b|--simulatebatch</b></p>
<p style="margin-left:17%;">In stead of the normal
simulation of an average arrival rate, run everything in a
busy loop without any waiting/queuing taking place. You
typically do this with much fewer threads (and/or processes)
as each thread in each process constantly will be executing
emulated business transactions.</p>
<p style="margin-left:17%; margin-top: 1em">Note that all
burst features are turned off and that only the processing
in the normal pool (set via pool_type in your project file)
is done. You should normally arrange for your connections to
be dedicated and set pool_type:="dedicated", but
if you do use e.g. sessionpool, sessions will constantly be
acquired and released.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-g|--graphs|-G|--qegraphs</b></p>
<p style="margin-left:17%;">Show graphs during the run
using gnuplot’s output to X-Windows. This requires a
properly set DISPLAY environment variable. The two latter
options causes an alternative graph; see <a href="oltprun.html">oltprun(2rwl)</a>.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-p|--runnumberfile
file</b></p>
<p style="margin-left:17%;">Put the runnumber into file
(default runnumber.txt)</p>
<p style="margin-left:11%; margin-top: 1em"><b>-s|--startseconds
file</b></p>
<p style="margin-left:17%;">Put the startseconds into file
(default startseconds.txt)</p>
<p style="margin-left:11%; margin-top: 1em"><b>-R|--runfile
file</b></p>
<p style="margin-left:17%;">In stead of using the normal
run.rwl file count in the oltp directory, use the file
named. The primary use of this is for experiments that
require modifications to run.rwl.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-a|--preallocate</b></p>
<p style="margin-left:17%;">If your orders and order_items
tables are partitioned, you can use the -a option to make
sure an empty set of partitions are created at the start of
the run. Only use this if the automatic allocation via
interval partitions appears to cause trouble</p>
<p style="margin-left:11%; margin-top: 1em"><b>-o|--extraoutput
file</b></p>
<p style="margin-left:17%;">Add the contents of the named
text file to generated html output; this can be used if you
want to add more information than feasible using
komment.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-i|--integer|-d|--double
spec</b></p>
<p style="margin-left:17%;">Provide the option to rwloadsim
when doing the actual run, i.e. when run.rwl (or the file
given as the -R option) is executed.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-W|--awrwait</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>-K|--awrkill
n</b></p>
<p style="margin-left:17%;">See below under COMPLETION</p>
<h2>COMPLETION
<a name="COMPLETION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Under normal
circumstances, all the processes started by oltpcore should
complete, and it should therefore be feasible to simple have
a "wait" at the end of the script. If, however,
one or more of the processes take an unexpectedly long time
to complete or even never completes, such a "wait"
would also not complete (in reasonable time). Therefore,
oltpcore has a mechanism that will kill processes taking
longer than expected. For most processes that do actual
simulation work, a consequence of this is simply that the
process gets canceled, but for the process gathering awr and
other system statistics, it means no awr will be produced.
Oltpcore therefore waits as long as possible until killing
the awr gathering process, but it will do so eventually. If
you find that your awr reports does not get created even
when things otherwise are running normally, you can change
the behavior in one of two ways:</p>
<p style="margin-left:11%; margin-top: 1em">By using the
<b>-W</b> option, oltpcore will <i>always</i> wait for the
awr gathering process which does increase the risk that some
system failure will cause oltpcore to wait for a very long
time or even not complete.</p>
<p style="margin-left:11%; margin-top: 1em">By using the
<b>-K nn</b> option, you can change the default time of 15s
before the final kill will be performed. The implication is
that if there are processes to be killed, the final wait
time (and therefore total execution time) will be longer,
but oltpcore is guaranteed to complete.</p>
<h2>USAGE
<a name="USAGE"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The
<b>oltpcore</b> command shows stdout and stderr to the
terminal, so you can immediately see any errors, but only
stdout will be save to a file. You should therefore only use
this command initially while you verify everything is
working as expected. Otherwise, always use the <a href="oltprun.html">oltprun(2rwl)</a>
command that makes both stdout and stderr available for
later browsing, but only outputs stdout to the terminal.</p>
<h2>COPYRIGHT
<a name="COPYRIGHT"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Copyright
© 2023 Oracle Corporation <br>
Licensed under the Universal Permissive License v 1.0 as
shown at https://oss.oracle.com/licenses/upl</p>
<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><a href="oltpsetup.html">oltpsetup(2rwl)</a>,
<a href="oltprun.html">oltprun(2rwl)</a></p>
<hr>
</body>
</html>