When you open a schedule, you can set these properties.
- Number of users
- Sets the initial number of users in a run. You
can increase this number once the run starts.
- Add a delay between starting each user
- A delay lets you further control user actions.
For example, you might want to slow down the initial startup of multiple users.
- Stop running the schedule after an elapsed time
- Lets you gather performance data over
a specific time.
- Modify the duration of think time delays
- Lets you increase, decrease, or randomize think
timeāor to play it back exactly as recorded.
- Limit think times to a maximum value
- Lets you supply a maximum value for the think
times of virtual users.
- Execution history log level
- The execution history is a single file
that shows all events that occur during a schedule or test run. The level
of history that you set determines whether you receive individual response
time statistics for Percentile reports and information on verification points.
- Statistics log level
- Lets you set the type of data that you see during
a run and the sampling rate for that data, and whether data is
collected from all users or a representative sample.
- Problem determination log level
- Lets you set the level of information logged during
a run. By default, only warnings and severe errors are logged. Typically,
you change this log level only when requested to do so by IBM Software Support.
- WebSphere Studio Application Monitor
- If you have WebSphere Studio Application Monitor
(WSAM) installed, you can create and view WSAM reports.
- Enable ARM
- This item appears if the IBM Performance Optimization toolkit is installed.
Check this box to enable the schedule to collect profiling data for this toolkit.
At least one test in the schedule must have ARM monitoring enabled. For
more details, see "Collecting performance data from an application in an automated
test environment" in the IBM Performance Optimization toolkit documentation.
To set a sampling rate, select Only sample execution history
from a subset of users. The number or the percentage that you
select is applied to each user group. If you are running user groups at remote
locations, the number or percentage that you select is distributed evenly
among the remote locations.