Converse agora com nosso suporte
Chat com o suporte

Benchmark Factory for Database 8.1 - User Guide

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

Advanced

You can use the Advanced tab to specify the information to save in the Repository during a test run, to set error handling properties, and to specify database checkpoints for the test.

The repository is a database where all Benchmark Factory information is saved. It contains information about the transactions stored in each benchmark DLL and statistical information from benchmark executions.

To specify Advanced options

  1. In the New/Edit Job Wizard, select a test under Workload.

  2. Select the Test Options tab. Then select the Advanced tab.

  3. Specify advanced options. Review the following for additional information:

    Section

    Description

    Save results to Repository

    Select to save test information to the Repository. Then select one or more of the following options:

    • Save Real-Time Counter Information—Saves real-time performance monitoring information to the Repository during the test. See Performance Counters Tab for more information.

      Note: To specify sampling rate, go to Edit | Settings | Statistics | Real-Time counters.

    • Save User Statistics—Saves user-level statistics.
    • Save Distribution—Saves transactions per second and response time per user distribution.

    • Log Transaction Results to disk—Logs the transaction results of a job to disk.

      Note: Checking this option imposes performance penalties.

    Error Handling

    Stop test after first error—The test is stopped when an error is reported.

    You can specify a default setting in Edit | Settings | Error Handling. See Error Handling Settings.

    Execute the following program at the beginning of each iteration

    (Available only for benchmark tests and some capture/replay tests.)

    Browse to and select the file to execute at the beginning of each iteration.

    Note: This field accepts BFScripts.

    Enforce Timeout—Select and enter a time to enforce a timeout on the file executing.

    Execute the following program at the end of each iteration

    (Available only for benchmark tests and some capture/replay tests.)

    Browse to and select the file to execute at the end of each iteration.

    Note: This field accepts BFScripts.

    Enforce Timeout—Select and enter a time to enforce a timeout on the file executing. If the file does not complete in the specified time, it is stopped and the job continues.

    Database Checkpoints

    Perform checkpoint at start of each test iteration—Initiates a database checkpoint at the beginning of a test iteration.

    Perform checkpoints during each iteration—Initiates a database checkpoint during a test iteration.

    Number of checkpoints—Specifies the number of checkpoints to initiate.

Options (Capture/Replay)

Settings on the Options tab allow you to apply scaling to the user scenarios (transactions) for a particular test.

To apply scaling to user scenarios

  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 Options tab.

  3. Modify options. Review the following for additional information:

    Enable Userload scaling (simulation)

    Select to enable scaling for all user scenarios in the selected test.

    • Move the slider to the right to scale up userload for all scenarios (transactions) during playback.
    • You can also specify the number of users per scenario in the Transactions tab. See Transactions Tab for more information.
    Execute by time Sets the time and length of the capture replay test.

Add SQL Transactions

The Add SQL Transactions function allows you to add a SQL statement transaction to a test in the Job workload.

To add a SQL statement transaction to 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. Select Add SQL Transactions from the Add SQL Transactions drop-down list.
    • Or select a user scenario and click to open the list of SQL transactions. Then select Add SQL Transactions.
  4. The Add SQL Transaction dialog opens. Do one of the following:

  5. Modify the remaining options on the SQL Statement tab. Review the following for additional information:

    Statement Name Enter a name for the statement, or use the default.
    Execution Method

    Select an execution method for the SQL statement.

    • Prepare and Execute SQL—Prepare the SQL and execute immediately after preparation.
    • Prepare SQL Only—Prepare SQL without executing.
    • Execute already prepared SQL—These transactions will run the SQL statement contained with the reference prepared SQL when called. If the statement has not been prepared, an error will generate.
    Click to execute the SQL statement. See Run SQL Preview for more information.

    Click to add a bind variable.

    • Select the Bind Parameters tab and then click or double-click within the Bind Parameters window to add a bind variable and value.
  6. Select the Latency tab to specify latency values for the SQL transaction. See Specify Latency for more information.
  7. Click OK in the Add SQL Transaction dialog to the save the SQL statement and add it to the test.

Add User Scenario from XML

Benchmark Factory allows you to import and execute SQL from an .xml file. When you attempt to import very large Oracle trace files into Benchmark Factory, they are converted to editable .xml files.

You can edit the .xml file in the Benchmark Factory Session Editor.

To add SQL from an XML file

  1. In the New Job or Edit Job wizard, select the transaction step to which you want to add a user scenario from a file. Then select the Transactions tab.
  2. In the Transactions tab, click the Add User Scenario button and select Add From Session Metafile in the drop-down list. Then click . The Add User Scenario dialog opens.
  3. Select the User Scenario tab in the Add User Scenario dialog. Then click to browse to and select an .xml file containing the SQL you want to import.
  4. Click OK to add the User Scenario.

To edit SQL statements in an XML file

  1. After selecting the .xml file in the Add User Scenario dialog, click Edit. Or select the scenario in the Transactions tab and click Edit.

  2. The .xml file opens in the Benchmark Factory Session Editor.

  3. Under Session Details, select the SQL statement you wish to edit. The statement displays in the SQL Statement view.

  4. From the SQL tab, you can click in the upper right-hand corner to:

    To adjust latency, select the Latency tab. See Specify Latency for more information.

 

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação