Applies to LoadComplete 4.97, last modified on May 20, 2019

You can apply expected service level agreement (SLA) criteria to load tests to ensure that your web site meets the performance objectives.

You set performance thresholds for a load test on its SLA page. (To define performance thresholds for individual operations in scenarios the test simulates, use the Scenario editor.)

The page contains the following settings:

  • Max Page Load Time (ms) – The maximum acceptable load time for pages during the test run.

  • Max Time to First Byte (ms) – The maximum acceptable time to first byte for requests during the test run. This criterion is also applied to WebSocket messages.

If the specified limits are exceeded during the test run, LoadComplete will report an SLA criterion violation and post an error message to the test log. During the test run, you can view the number of violations on the Runtime > Graphs page.

If the scenarios your load test simulates have SLA criteria specified for individual operations, they will override the criteria you specify for the test.

If you disable service level agreement monitoring for your load test, LoadComplete will use the thresholds specified for individual requests, pages and WebSocket messages in the scenarios you use in your load test (if any criteria are specified). If service level agreement (SLA) monitoring is disabled both in the test and in the scenarios, LoadComplete does not monitor violations.

For tips on defining website performance thresholds for load testing, see Setting Reasonable Goals for Service Level Agreement.

To learn how to configure a load test to stop when the specified error limit is reached, see Stopping Tests on Errors.

See Also

Setting Reasonable Goals for Service Level Agreement
Setting Service Level Agreement (SLA) Criteria
About Load Test Editor
Load Profile Settings
Continuous Load Settings
Stopping Tests on Errors

Highlight search results