Command line Usage

This page describes how to use the benchmark controller from the command-line.

Usage

Options

--config=/path/to/configuration.file

Path to an optional driver configuration file. The configuration file follows the standard Python ConfigParser format. If this option is not provided, then the driver will be given the configuration parameter that is returned by the makeDefaultConfig() function.

--reset

If this option is provided, the controller will set the reset flag in the configuration dict to true. The driver is responsible for resetting the database contents in the loadConfig() function.

--scalefactor=<float>

The scale factor for the benchmark data. The default value is 1.0, which means that the data size will be according to the TPC-C benchmark specification. A value greater than 1.0 means that less tuples will be inserted into the database in the loading phase, whereas a value greater than 1.0 means that more tuples will be inserted.

--warehouses=<int>

The number of warehouses to use in the benchmark for both the loading and execution phases. Use the scalefactor parameter to control the number of tuples created per warehouse. Default is four.

--duration=<int>

This option specifies how long to the execution phase of the benchmark (in seconds). This time does not include the time it takes to load data, or invoke the various callbacks. The default duration is 60 seconds.

--ddl=/path/to/tpcc.sql

Alternate path to the the TPC-C DDL file. This is provided in case a driver needs a custom DDL.

--clients=<int>

The number of blocking clients to fork when executing the transaction workload portion of the benchmark. Default is to use just one client.

--stop-on-error

When this option is provided, each client executor will halt if the driver throws an assert or exception during execution.

--no-load

If this option is provided, the controller will not invoke any of the loading phase functions.

--no-execute

If this option is provided, the controller will not invoke any of the execution phase functions.

--print-config

Causes the controller to print out the default configuration file provided by the given driver and then exits immediately without loading any data or executing transactions.

--debug

Enables debug log messages.