Response time refer to the time takes for one system node to respond to the request of another. It is time a system or a system unit takes to react a specific input until the process is over. For example, you have API, and you want to know exactly how much time it takes to execute it and return data in JSON
Response Time measures the performance of every single transaction or query. Response time starts when a user sends a request and ends when the time that the application states that the request has completed.
In this tutorial, you will learn
- What is Response Time?
- How to Measure Response Time?
- Types of Response Metrics
- Three important response time values
- Response Time testing tools
Response time is measured with the help of a test tool by surrounding an important business process with Start and End transactions. A business process may be an action or set of actions which user performs in an application to complete a business task. Some example would be login to the application or a book purchase on Amazon.com.
For the same process, the response will vary slightly from tool to tool. Here is why
- Method of calculating metrics gathered by each tool
- Simulate and Capture the load which can make a difference in the response time
- Extra Items recorded when generating user loads
- Computing metrics gathered by each tool increases the response time
- The architecture of the two tools may be different
|Response Time Metrics||Explanation|
|Peak Response Time||The Peak Response Time helps us to find potentially problematic components. It helps us to find all the all the irregularity in the website or system where a certain request is not handled correctly. For example, there may be a large database query executed which can affect the response time. This query does not permit the page to load at the desired time.|
|Error Rate||The Error Rate is a mathematical calculation which displays the percentage of problem requests against all requests. This percentage counts all HTTP status codes displaying an error on the server. It also counts requests which are time out.|
Response time testing has two most essential characteristic:
- Average response time
- Maximum response time.
It shows how long a user needs to wait for the server to the response its request.
Following are key response time values
|0.1 Second||It is most preferred response time. If the response time is 0.1, users always feel that the application or system is responding instantly, and do not feel any interruption.|
|1.0 Second||It is the defined as the maximum limit of acceptable response time. Users are unlikely to feel any interruption, though they may experience some delay. The response time of more than 1-second may interrupt user experience.|
|10 Seconds||It is a maximum limit after which response time goes beyond the acceptable limit. However, in today's time, if response time exceeds 6 seconds, the user will leave that site or quit the application.|
Generally, response time should be fast as possible in the interval of 0.1 - 1 second. However, people can adapt to slower response times, but they will never be happy with a response time greater than 2 seconds.
There are many Response Time testing tools are available in the market. Three most prominent names are:
Jmeter can be used for load and performance testing.
Download link: http://jmeter.apache.org/download_jmeter.cgi
2) Load Runner:
Load Runner is a load testing product developed by Microfocus. LoadRunner response testing tool works on the principle of simulating Virtual Users on the subject application.
Adobe Experience manage which is shortly known as AEM is another effective tool for testing response time. It allows checking problematic queries, request and error message.
- Response time refer to the time take for one system node to respond to the request of another
- The Average Response Time is the average time taken for every round trip request
- Peak Response Time helps us to find that what components are potentially problematic.
- The Error Rate is a mathematical calculation which displays the percentage of problem requests.
- Three crucial response time values are: 0.1 seconds, 1.0 second and 10 seconds
- Three most used response time testing tools are Jmeter, LoadRunner, and AEM.