Think Time

Think Time: The Time between two transactions or user actions.

A real-world user takes some time to perform his activities on a web application. Such activities involve reading the content of a page, entering the details on a web form, selecting a product from a list etc. While doing these activities, a time gap creates between two actions of a user and this time gap is known as Think Time. Think time simply defines as the time taken by a user to think and perform the next action on a web application.

Let’s take an example: A user launches Facebook in the browser, resulting in the login page of Facebook appearing. He takes 5 seconds to enter his login email, and password and hit the Login button. Hence these 5 seconds will be considered as a think time of the user for the Login page.

Why Think Time is Required?

A real user never does all the actions like login, search, placing an order, payment, logout etc. within a few seconds. Definitely, he requires some time to read, write, think and perform the next action. To simulate the same situation, a performance tester inserts a time delay i.e. Think Time between two transactions. Like this, he creates a real-world scenario in the test environment.

Another reason is if a performance test executes without Think Time then it is like bombarding the server without any pause. This may fail the server and provide the wrong result for server capacity. In reality, think time halts the virtual users for a defined period of time before sending the next request. Also, it helps the server to process the request in a proper manner and provide production-like results.

Note: Apart from Think Time, Pacing, user load and TPS are also involved to design an accurate scenario for performance checks.

Where to add Think Time in the script?

Think time is always inserted between two transactions in the test script. The count of the think time function/component is always one less than the count of transactions. For example, a script has 3 transactions which are login, search and log out then the flow is like this:

Login->Think Time->Search->Think Time->Logout

Do not add think time at the start or at the end of the user journey because practically there is no such situation. Think time always comes in between a user session.

How to decide the value of Think Time?

Think time value depends on the length of content available on the web page. An average Think Time could be in the range of 3 to 10 seconds for a normal user. Think time value should not be so large else this may impact the target TPS and should not be too small else this may impact server performance.

Think time helps to achieve the concurrency of the user session on the server. It extends the user session on the server. Therefore too large think time holds the session and restricts the server to create a new session (in case of server capacity is reached). Too small think time or no think time causes frequent user session creation and less user concurrency.

Also, Refer >> Think Time Calculator

2 thoughts on “Think Time”

  1. The value of think time will also depend on the user’s familiarity with the application. eg: A call center employee who uses the same application day in and day out will have less think time compared to a end user website which will have more number of 1st time users.


Leave a Comment