Should I configure Step Download Timeout?
Posted: April 22nd, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: Scripting, Step Download Timeout | No Comments »Previously, in article, “Error -27728: Step download timeout (120 seconds) has expired when downloading non-resource(s) [MsgId: MERR-27728]” for Step Download Timeout error and the referencing materials that can be useful to you. Here, we are going to touch on the “What should I do?” question.
1. Tell your clients/users that the application failed to respond in the 120 secs time frame
Well, straight-forward. This is because it failed the 120 secs benchmark, an equivalent of 2 mins. Imagine a normal application not responding within 2 minutes is serious where we are anticipating an average respond time of 10 secs!. However, take note that if your application can respond more than 120 sec, then consider the next suggestion.
(Source: Jakob Nielsen, Response Times: The Three Important Limits)
2. Set the Step Download Timeout to 999 secs
This was brought out in the LoadRunner Yahoo Group. Why 999 secs? The benefit of doing this is that you are able to determine the response time from the application in the 999 seconds limit without allowing it to fail. This is good when you want to measure the actual timing without defining a benchmark.
3. Limit the Step Download Timeout to the expected response time
For this, discuss with your clients/users about the requirements for expected response time. Once you gotten the information, configure the Step Download Timeout accordingly to the expected response time. In this way, you are able to tell if the application pass or fail immediately against the expected response time. But if your clients/users wants to know the actual time taken, then it would be advisable to follow the suggestion in point [2].
Hope this will help you have a better understanding on the impact when you configured the Step Download Timeout and assist you in your followup actions.
Leave a Reply