oltpforever, oltpforever2 − Execute oltprun until canceled
oltpforever [-H|--help] [-g|-G] [-a] [-k key] [-R file] [-r n] [-s n] [-S ’n1 n2 ...’][-K n] [-W] [komment text ...]
oltpforever2
Execute 1h long runs of the oltp workload until canceled.
-H --help
Print short help.
-k|--key key
Set the key that will be used when storing results in the repository database. The default is the same as the project name.
-g|--graphs|--qegraphs|-G
Show graphs during the runs using gnuplot’s output to X-Windows. This requires a properly set DISPLAY environment variable. For details, see oltprun(2rwl).
-R|--runfile file
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.
-s|--sleep
seconds
-S|--sleep-sequence ’sec1 sec2 ...’
Normally, oltpforever starts the next oltpcore execution as soon as the previous one has completed; if you provide the first option, there will be an extra sleep between each oltpcore. This can be used to have an extra period between runs without activity if you don’t start oltpforever2.
The second is option is similar to the previous one, but in stead of sleeping for the same number of seconds after each run, the values provided to this option (that must be embedded between quotes for proper processing by the shell) are used in a round-robin sequence. These times are added to the value given by the -s option.
The first run will always start immediately and the extra sleep will be applied starting with the second run.
As an example, if you give the options -s 60 -S ’0 30 60’ there will be sleeps of 60, 90, 120 seconds after the second, third, fourth run and again after the fifth, sixth, seventh run etc.
-r|--runperiod seconds
By default, oltpforever is making sure there is continuous workload against the database by making runs lasting close to 1h by using oltpforever2 as explained below. You can alternatively provide a different run period for each run using this option, in which case it is suggested that you do not start oltpforever2.
If you goal as an example is to investigate initial ramp up effects during repeated runs, use the --runperiod option combined with either of the two sleep options.
-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
-W|--awrwait
-K|--awrkill n
See COMPLETION at oltpcore(2rwl).
If your goal is to see progression over long time, you can use the oltpforever command to do so. It does little more than repeatedly doing oltprun making 3590s long runs. The process count for these runs is found in the parameter file which means you can change it without interrupting the oltpforever run. To stop the run after the next completion, remove the file named after your project with a .run suffix. Alternatively, simply hit ctrl-c, which however will terminate the last run prematurely without cleanup and without executing oltpplot. You can provide additional text for your generated html and graphic files by adding extra arguments to the oltprun command.
Note that there will be a period between the runs where your database under test has no workload, and that you can make this period longer using the -s and/or the -S options. If you want a continuous workload, you can execute oltpforever2 (that does not take any options) within the first ½ hour of starting oltpforever; simply start it in a new session. The latter will then execute the same workload continuously until stopped or canceled using ctrl-c) but shifted ½ hour from the former to ensure a continuously loaded database. Do not use the -s or -S options if you intend to run oltpforever2. If using oltpforever2 you should adjust the number of processes accordingly taking the double load from the two executions into account.
If running for extended periods, the time difference between the two may drift slightly, in which case you may need to restart both.
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), oltpday(2rwl)