Skip to end of metadata
Go to start of metadata

In a client-server environment, the time it takes to complete a transaction can be broken down into two categories:

  • server time: the time it takes for the server to complete processing incoming client requests. This time changes with different load levels (number of VUs).
  • client time: the time it takes for client rendering and script execution. This time is typically constant with different load levels.

Generally, load testing measures server time since it depends on the number of VUs. However, it is sometimes beneficial to include client time in the performance metrics when measuring transaction performance.

In StresStimulus, this can be accomplished by adding a delay equivalent to the amount of time client execution took place.

Adding the delays

There are two ways to add client execution delays.

From the wizard

In the test wizard > Think Time > Click Add client execution delays button.

From the test case tree

In the test case tree,> right click on test case > Select Add client execution delays menu item.


After adding the client execution delays, a delay object will appear for every corresponding client delay. The recorded waterfall diagram shows that each gap between requests will be represented by a delay on the test case tree.

The delay object will have the following properties:

Delay: calculated client execution delay time

Description: Recorded client execution delay

Include in transaction time: Yes


  • No labels