The Load Test Optimizer appears in the Registry Monitor and lets you run a simple load test on the system under test. A load test determines how many users the system under test supports.
In the Load Test Optimizer, the system under test runs continuously. More simulated users continue to access it, until a specific target is reached. This target is typically a predefined average response time.
The Load Test Optimizer helps determine how many users the system under test supports. An optimizer can be set on any DevTest metric, such as average response time. An optimizer can also be set on a metric pulled from an external source, such as SNMP, JMX, or Windows Perfmon. The number of users increases at a preset frequency and informs you when a preset metric threshold is achieved. For example, you can increase the number of test instances by 5 instances every 10 seconds until the average response time hits 2 seconds.
To optimize the test, it must be running.
To configure and start an optimizer:
.
The Optimizer panel opens with the name of the staging document at the top.
The metric to use for the optimization. Select from the pull-down list.
The simulator that is used to spawn test instances. Select from the pull-down list.
The metric value at which the optimizer reports that the system requires more virtual users. Enter a numeric value.
The metric value at which the optimizer reports that the system cannot support any more virtual users. Enter a numeric value.
The number of extra virtual users to add to the system at the update frequency. Enter a numeric value.
The number of milliseconds between increments
.
As the optimizer increases the number of virtual users, the number of virtual users display on both the Optimizers section and in the Instances column of the Tests tab in the Registry Monitor.
As the optimizer executes, you can change the parameters. To update the optimizer with the changed information, click Update 
.
.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|