1. Configure and Run Autopilot

To begin configuring Autopilot mode follow the steps described in the previous Chapter for Running OLTP Timed Tests before creating and running the Virtual Users, these will be configured automatically. Select Autopilot Options from the tree-view as shown.

Figure 5.1. Autopilot Options

Autopilot Options


This shows the Autopilot Options Dialog.

Figure 5.2. Autopilot Options

Autopilot Options


Configure the Autopilot options in the same manner as you would use to instruct your Virtual DBA:

Table 5.1. Autopilot Options

OptionDescription
Autopilot Disabled/Autopilot EnabledThis Autopilot Disabled/Autopilot Enabled Radio buttons give you the option to select whether the Autopilot button is enabled on the main window.
Performance Profile IDSet to a positive integer to group the Jobs for a sequence together to be viewed as a performance profile in the Job viewer.
Minutes per Test in Virtual User SequenceThe minutes for test duration defines the time interval between which your virtual DBA will create the Virtual Users, stop the test and create the next Virtual Users in the sequence. You should configure this value in relation to the Minutes for Ramup Time and Minutes for Test Duration given in the Timed Test options. For example if the values in the test script are 2 and 5 minutes respectively then 10 minutes for the Autopilot Options is a good value to allow the test to complete before the next test in the sequence is run. If the test overruns the time interval and the Virtual Users are still running the sequence will wait for the Virtual Users to complete before proceeding however note any pending output will be discarded and therefore for example if the TPM and NOPM values have not been reported by the time the test is stopped they will not be reported at all.
Virtual User Sequence (Space Separated Values)The Virtual User Sequence defines the number of Virtual Users to be configured in order for a sequence of tests separated by the Minutes for Test Duration. Note that for a Timed workload the Monitor Virtual User will be added and therefore the sequence defines the number of active worker Virtual Users. Therefore in this example the actual users running the workload will be 1, 2, 4, 8, 12, 16, 20 and 24 however and additional one will be created.
Virtual User OptionsThese values are exactly the same as set when defining the Virtual User Options, you should ensure that Output is enabled and configure preferred logging options.

Double-click on the Autopilot Icon to begin running the sequence of tests

Figure 5.3. Run Autopilot

Run Autopilot

The Autopilot Window is shown tracking the Monitor Virtual User output and the time interval, no further interaction is required.

Figure 5.4. Autopilot Running

Autopilot Running

After the first test HammerDB reports the output and then configures the Virtual Users and runs the second test automatically.

Figure 5.5. Autopilot Continuing

Autopilot Continuing

When the sequence is complete you will see the message Autopilot Sequence ended. You can now view all of your test results in the Job Viewer.

Figure 5.6. Autopilot Complete

Autopilot Complete


If you set a performance profile ID you will see your Jobs in the Job viewer and a Performance Profile summary identifying the top performing job, with the NOPM, TPM and Maximum Active Virtual Users (AVU).

Figure 5.7. Autopilot Performance Profile

Autopilot Performance Profile

Clicking on the profile id shows a graph of the NOPM and TPM for all of the jobs in the autopilot sequence.

Figure 5.8. Performance Profile

Performance Profile