3. Run a Test Workload

Note that HammerDB stores all output of a workload called Jobs within a SQLite database for later retrieval. As a test workload prints a considerable amount of output for performance you can disable the storage of the Jobs under the Jobs tree view option, clicking Jobs Disabled and restarting HammerDB. If you leave Jobs enabled it is expected that the performance of the test workload is slower as all of the output is stored in SQLite.

Figure 2.8. Disable Jobs

Disable Jobs

After restrarting, within the tree-view Select Driver Script Options and Settings. Leave the settings at Test Driver Script and click OK

Figure 2.9. Driver Connection Options

Driver Connection Options


Observe that the Driver Script is Loaded. Clicking on Load will reload the script.

Figure 2.10. Driver Script Loaded

Driver Script Loaded

Further down the tree-view under Virtual User select Options and select "2" for the number of Virtual Users, click OK.

Figure 2.11. Virtual User Options

Virtual User Options

Click on Create and the Virtual Users will be created and waiting to run in an idle status. (Clicking run first will run both Create and Run Immediately).


Figure 2.12. Virtual Users Created

Virtual Users Created


Double-click on Run - you can now observe the Virtual Users running a workload against the database. When ready press the red stop button to stop the workload.

Figure 2.13. Virtual Users Running

Virtual Users Running