This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Setting up workloads

In the Workload Configuration dialog box, you can specify the following:

  • Number of users per script
  • Simulation time
  • Ramp-up time
  • Measurement time
  • Type of workload to run

To open this dialog box, right-click Workload in the left navigation bar, and choose Edit active workload in the pop-up menu.

SilkPerformer Workload Configuration dialog box

(Click the image to expand it.)

Increasing workload is used most of the time. It enables you to ramp up users successively. For more information about workload types, search for "workload models" in the SilkPerformer Help.

In the above figure, 200 virtual users are divided among seven scripts. A user ramps up every 5 seconds. The simulation runs about 49 minutes, and measurements are taken after all users have logged in at least once.

A queuing workload is used when you know the specific amount of work that needs to be done in a particular time period.  For example, you know that every hour approximately 20 new Incidents are created.  You would specify 20 as the script transaction frequency.

For more information about these settings, search for "workload definition" in the SilkPerformer Help.


When you create a workload, make sure you use the correct profile. The active profile should be shown in bold in the left navigation pane of SilkPerformer.

You can create as many workloads as necessary, but only one can be active.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.