Chat now with support
Chat with Support

Benchmark Factory for Database 7.6 - User Guide

Getting Started Overview of Benchmark Factory Benchmark Factory Components Agents Connections Create and Edit Tests and Jobs Test Results and Run Reports Troubleshooting Licensing REST API

Test Options - Transactions

Transactions

The Transactions tab of the Edit Job or New Job Wizard allows you to modify the transaction mix, add or delete user scenarios, add or delete transactions, or modify SQL for the selected test in the job.

To modify the transaction mix in a test

  1. In the Edit Job or New Job Wizard, select a test under Workload in the left pane.
  2. From the Test Options tab, select the Transactions tab.
  3. Use the Transactions tab to modify transactions and/or transaction mix for the selected test. Review the following for additional information:

    Click to edit the selected user scenario or transaction. The scenario/transaction opens in a dialog for editing. When editing a scenario or transaction, you can:

    • Review the list of SQL in the user scenario.
    • Review the benchmark transaction.
    • Add additional transactions to the user scenario.
    • Delete SQL or transactions from the user scenario.
    • Edit a SQL statement or its bind parameter.
    • Specify latency for each SQL, each transaction, or for the user scenario. See About Latency for more information.
    Move the selected item up or down in the list in the Transaction tab.

    Transaction Tab Columns

    Review the following column descriptions for the Transaction tab.

    Weight column—(Transactions) The likelihood a transaction executes by a virtual user. (Not available in Test SQL for Scalability.)

    • Transaction weight definition: If a test has two transactions, A and B, with A having the weight of one and B having the weight of six, transaction B will run six times for every time A runs once. The run order is randomly generated for users.

    Percentages column—(Transactions) Transaction's weight as a percentage or the total weight. (Not available in Test SQL for Scalability.)

    Users—(User scenarios) Displays the number of users tested during replay for this scenario. Double-click to edit.

    Executions—(User scenarios) Displays the number of executions for this scenario. Double-click to edit.

    Ave. number of statements per commit (Replication test only) Specify the number of statements to include in a commit. Use this option to attempt to simulate typical transactions.
    Add SQL Transactions

    Add additional transactions to the test. Select one of the following from the drop-down list and then click .

    Add User Scenario

    Add a new user scenario to the test. Select one of the following from the drop-down list and then click .

    • Add User Scenario—Add a new user scenario and then populate it with transactions (from one of the categories listed above).

      Note: You can right-click a User Scenario and select Replace Child Latencies. See Replace Child Latencies for more information.

    • Add From Session Metafile—Add a user scenario by importing a transaction file.
    Replay User Load Add a new scenario to the test by importing a workload from an Oracle trace file, a SQL Server trace table, an ODBC trace file, or a text file.

    Note: New user scenarios/transactions are added to the top of the list. Use the up and down arrows to rearrange the order of items in the list.

User Load

The User Load tab of the New Job or Edit Job Wizard allows you to specify the number of virtual users for each iteration of a test.

Note: To set default values for User Load, go to Edit | Settings | User Load. If you modify the default settings, the changes will apply to new jobs only, not to existing jobs.

 

Section

Description

User Load

Add Single User Load—Specify a single user load, then click Add to add it to the selected user loads.

Add a Range of User Loads—Specify a range, then click Add to add the range to the selected user loads.

Timing

Use the Timing tab to specify timing phases associated with a test.

 

Section

Field/Icon

Description

Time Phase

Total Iteration Length

The composite of the Pre-Sampling and Sampling time.

 

Pre-Sampling

The length of time users execute transactions in order to reach a steady state before statistics are collected.

 

Sampling

The length of time used to collect statistics while the users are executing transactions.

User Startup

Start all users as quickly as possible

Starts all users immediately after a test begins.

 

Start all users at even intervals for

Sets the amount of time in which to start all users at even intervals. The interval duration is equal to this value divided by the number of users.

 

Start a new user every [n] seconds

Starts a new user, then waits the entered number of seconds before starting the next user.

Related Documents