oltpscale − Perform several runs and finally a scaling graph
oltpscale [-H] [-g|-G] [-a] [-A] [-k key] [-r runperiod] [-b] [-l lo] [-h hi] [-i int] [-K n] [-W] [-R file] [komment text ...]
Execute a series of runs with increasing number of processes and produce a scalability report with graphs, etc.
You can alternatively use the gnu style long options shown below.
-H --help
Print short help.
-l --loprocess N
Set the lowest number of processes and the increase in process count between runs.
-i --interval N
Set the increase in process count between runs; default is the same as the lowest process count.
-h --hiprocess N
Set the highest number of processes being used in one run.
-n --processcount N
Execute this as a scaling run, but with only one actual run having this many processes.
-k --key key
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 must be unique for your host as there otherwise would be results from several overlapping/identical runs in the same scaling report.
-A --allowreuse
Allow reuse of key; this should only be used if you know there will be no repetition of runs with same process count.
-r --runperiod N
Set the runperiod in seconds for each run; the default is 595s.
-b|--simulatebatch
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.
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.
-g|--graphs|-G|--qegraphs
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 oltprun(2rwl).
-a|--preallocate
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
-R|--runfile file
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.
-W --awrwait
-K --awrkill n
See COMPLETION at oltpcore(2rwl).
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.
To verify that a key does not already exist from your host, use oltpcheckkey.
Copyright
© 2023 Oracle Corporation
Licensed under the Universal Permissive License v 1.0 as
shown at https://oss.oracle.com/licenses/upl
oltp(2rwl), oltprun(2rwl), oltpcheckkey(2rwl), oltpscalereport(2rwl)