Skip to end of metadata
Go to start of metadata

A physical user typically spends some time on each page to analyze the displayed information or enter data. The delay between opening a page and navigating to a subsequent page is called think-time. Think-time is an essential factor in realistic load tests. You can customize page think-times to emulate different users’ iteration for a more realistic load test. The following think-time mode options are supported.

Transactions, also have think-time that are handled the same way as pages. The properties and values that apply to page think-times also apply to transactions.

Think Time ModeDescription
ZeroNo think-time is used. This is generally not recommended for load tests because it results in an abnormally high load on the tested website. Use this option when a maximum load is required in stress tests.
Object-level

The think time specified in each page or transaction will be used. You can modify the property by selected the page or transaction object in the test case tree and change the think time property in the property grid. The default value for pages is the recorded think time. When recording a test case, StresStimulus registers the time you spent on web pages and saves it in the page Think Time property.

ConstantConstant think time will be used. Another property will appear called Think Time (s), where you can specify a fixed value.
RandomWhen any of the previous options is selected, all VUs will exercise the same think time for pages. That never happens in real life. To make the test more realistic, use randomized think time for pages. When this option is selected, a random value in a given range will be used. Two properties will appear called Min Think Time (s) and Max Think Time (s) in which you can specify the think time range.



The think time is a delay inserted after the page or transaction is executed. Think time is not included in the page or transaction response time. The default think-time setting for pages is constant at 2 seconds, and the default for transactions is Object-level.

Higher think-times slow down the client request rate, which results in a lower server load. Increasing the think time will typically decrease the request rate and will allow the server to handle more virtual users.



  • No labels