Enhance a load test

This topic describes how to enhance a load test with SLAs and rendezvous points. You can also enhance a load test by adding disruption events. For details, see Disruption events.

Configuring SLAs

Service level agreements (SLAs) are specific goals that you define for your load test run. After a test run, OpenText Core Performance Engineering compares these goals against performance related data that was gathered and stored during the course of the run, and determines whether the SLA passed or failed. Both the Dashboard and Report show the run's compliance with the SLA.

On the SLA page, you set the following goals:

Goal Description
TRT (nth percentile)

The expected transaction response time, in seconds, that it takes the specified percent of transactions to complete. By default, the expected TRT is 3 seconds. If the percent of completed transaction exceeds the SLA's value, the SLA is considered "broken".

For example, assume you have a transaction named "Login" in your script, where the 90th percentile TRT value is set to 2.50 seconds. If more than 10% of successful transactions that ended during a 5 second window have a response greater than 2.50 seconds, the SLA is considered "broken" and shows a Failed status. For details about how the percentiles are calculated, see Percentiles.

Note:  The percentile goal for SLAs and all transaction measurements is set in Test settings > Run configurations. This is the percentage of transactions expected to complete successfully. By default, this value is 90%. For details, see Run configuration settings.
Failed transactions (%) By default, the percent of allowed failed transactions is 10%. If the percent of failed transaction exceeds the SLA's value, the SLA is considered "broken" and shows a Fail status.

You can set a separate SLA for each of your runs. You can also select multiple SLAs at one time and use bulk actions to apply one or more actions to the set.

You configure one of more SLAs (Service Level Agreements) for each load test:

To configure the SLA:

  1. In the Load tests tab, choose a test and click SLASLA pane button in the sidebar.

  2. By default, all transactions for the selected test are displayed, grouped by script name. If you want to remove the grouping and display transactions by transaction name, click the Group by button Group by button, and clear the Script name selection.

  3. Set transaction response time (TRT) settings:

    1. Set the expected time it takes the specified percent of transactions to complete. The default TRT goal is 3 seconds.

      The percentage of transactions expected to complete successfully is shown by the read only value displayed in the TRT (nth percentile) column header. This value is set in Test settings > Run configurations. For details, see Run configuration settings.

      Example: For example, if the TRT percentile is set to 90 and the TRT time value to 2.500 seconds, then if more than 10% of successful transactions that ended during a 5 second interval have a response time higher than 2.50 seconds, an SLA warning is recorded (using the average over time algorithm). For details, see Percentiles.

      Transaction response time example

    2. If you have run your test more than once, OpenText Core Performance Engineering displays a suggested TRT goal value.

      • To use the suggested goal value for a particular transaction, click the adjacent value button.

        Transaction goal example

      • To use multiple suggested TRT goal values, select the required transactions in the grid, and click Accept all.

        Mulitple TRT goals example

    3. Select the Stop checkbox to stop the test if the SLA is broken.

    4. If you do not want the TRT (percentile) goal to be used during the test run, turn off the Enable switch adjacent to the TRT (nth percentile) column.

      Note: For tenants created from January 2021 (version 2021.01), SLAs are inactive by default. You can enable them manually or click the Configure settings for multiple transactions button Configure settings for multiple transactions button to enable SLAs for multiple scripts. To change this behavior and have all SLAs enabled by default, submit a service request.

  4. Set failed transaction settings:

    1. If you want the Failed transactions (%) goal value to be used during the test run, turn on the Enable switch.

    2. Set the Failed transactions (%) goal value. The default goal value is 10%. If the number of transaction failures exceeds this value, the SLA is assigned a status of Failed.

  5. If you are not using the TRT (nth percentile) or Failed transactions (%) goal, you can hide the goal's column in the grid. To do this, click Select columns , turn off the switch of the unused goal, and then click Hide.

    Note: Hiding a column turns off the Enable switch for all transactions. If you later show the column, you need to turn on the Enable switch for all the transactions that you want to use (the setting values are retained).

  6. If you want your SLAs to be dependent on Vuser success, click the Vuser failure button Vuser failure button, and turn on the Set test status to Failed if one or more Vusers fail switch. The icon changes to when this option is on. If even one Vuser fails, it gives the test a Failed status.

  7. You can make bulk updates to your SLA settings.

    1. Select multiple SLAs at one time, and then click the Configure settings for multiple transactions button Configure settings for multiple transactions button. The icon number indicates the number of SLAs selected.

    2. Select the checkbox of each field that you want to update.

    3. Apply one or more settings to the selection by entering a setting value or changing the Enable switch (On/Off) settings.

      Tip: You can save values without updating them by clearing the checkbox.

      SLA multiple settings

    4. Click Apply to update the SLA settings.

Back to top

Setting rendezvous points

When performing load testing, you need to emulate heavy user load on your system. To help accomplish this, you can instruct Vusers to perform a task at exactly the same moment using a rendezvous point. When a Vuser arrives at the rendezvous point, it waits until the configured percentage of Vusers participating in the rendezvous arrive. When the designated number of Vusers arrive, they are released.

You can configure the way OpenText Core Performance Engineering handles rendezvous points included in scripts.

If scripts containing rendezvous points are included in a load test, open the Rendezvous pane and configure the following for each relevant rendezvous point:

  • Activate or deactivate the rendezvous point. If you deactivate it, it is ignored by OpenText Core Performance Engineering when the script runs. Other configuration options described below are not valid for deactivated rendezvous points.

  • Set the percentage of currently running Vusers that must reach the rendezvous point before they can continue with the script.

  • Set the timeout (in seconds) between Vusers for reaching the rendezvous point. This means that if a Vuser does not reach the rendezvous point within the configured timeout (from when the previous Vuser reached the rendezvous point), all the Vusers that have already reached the rendezvous point are released to continue with the script.

Note:  

  • The Rendezvous tab is only displayed if a script containing rendezvous points is included in a load test.

  • When you select a rendezvous point in the list, all the scripts in which that rendezvous point is included are displayed under the configuration settings. If the script is unavailable, its name appears dimmed.

  • If no rendezvous points are displayed for a script that does contain such points, go to Assets > Scripts and reload the script.

Back to top

See also: