-
Notifications
You must be signed in to change notification settings - Fork 19
Expand file tree
/
Copy patholtpscale.html
More file actions
205 lines (148 loc) · 6.19 KB
/
Copy patholtpscale.html
File metadata and controls
205 lines (148 loc) · 6.19 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
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Thu Sep 28 15:49:45 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>oltpscale</title>
</head>
<body>
<h1 align="center">oltpscale</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#OPTIONS">OPTIONS</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">oltpscale
− Perform several runs and finally a scaling graph</p>
<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>oltpscale
[-H] [-g|-G] [-a] [-A] [-k key] [-r runperiod] [-b] [-l lo]
[-h hi] [-i int] [-K n] [-W] [-R file] [komment text
...]</b></p>
<p style="margin-left:11%; margin-top: 1em">Execute a
series of runs with increasing number of processes and
produce a scalability report with graphs, etc.</p>
<p style="margin-left:11%; margin-top: 1em">You can
alternatively use the gnu style long options shown
below.</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>-l
--loprocess N</b></p>
<p style="margin-left:17%;">Set the lowest number of
processes and the increase in process count between
runs.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-i
--interval N</b></p>
<p style="margin-left:17%;">Set the increase in process
count between runs; default is the same as the lowest
process count.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-h
--hiprocess N</b></p>
<p style="margin-left:17%;">Set the highest number of
processes being used in one run.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-n
--processcount N</b></p>
<p style="margin-left:17%;">Execute this as a scaling run,
but with only one actual run having this many processes.</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 and will be
used as the base-name of the generated html scaling report.
Note that the key <b>must</b> be unique for your host as
there otherwise would be results from several
overlapping/identical runs in the same scaling report.</p>
<p style="margin-left:11%; margin-top: 1em"><b>-A
--allowreuse</b></p>
<p style="margin-left:17%;">Allow reuse of key; this should
only be used if you know there will be no repetition of runs
with same process count.</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
for each run; the default is 595s.</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>-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>-R|--runfile
file</b></p>
<p style="margin-left:17%;">In stead of using the normal
run.rwl file found 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>-W
--awrwait</b></p>
<p style="margin-left:11%; margin-top: 1em"><b>-K --awrkill
n</b></p>
<p style="margin-left:17%;">See COMPLETION at
<a href="oltpcore.html">oltpcore(2rwl)</a>.</p>
<h2>USAGE
<a name="USAGE"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">You typically
call this providing values for -k, -l and -h. The result
files (html and graphs) will include titles from your
parameter file, but you can provide additional text by
adding extra arguments to the oltpscale command.</p>
<p style="margin-left:11%; margin-top: 1em">To verify that
a key does not already exist from your host, use
oltpcheckkey.</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="oltp.html">oltp(2rwl)</a>,
<a href="oltprun.html">oltprun(2rwl)</a>, <a href="oltpcheckkey.html">oltpcheckkey(2rwl)</a>, <a href="oltpscalereport.html">oltpscalereport(2rwl)</a></p>
<hr>
</body>
</html>