Shulou(Shulou.com)06/03 Report--

Status quo: there was a problem during the performance / stress test, but I'm not sure it was my problem. It's still the programmer's program. huh?

Some friends who have just done performance testing are often at a loss when they encounter the following three errors in the Loadrunner Controller scenario when using Loadrunner for performance testing, because they are not sure if it is the programmer's problem. Or is it your own script? Because you have to prove yourself right before you can prove that others are wrong!

(1) Failed to connect to server "192.168.2.192"

General reason: your test environment is not conducted on the private network, but on the public network. The server on the public network can no longer receive requests from the client, but the client simulated by Loadrunner keeps sending requests to the server.

In addition, if the test is carried out in a local area network environment, then it is likely that the system really can not support so much concurrency.

(2) Server has shut down the connection prematurely

General reason: during the pressurization process, the tested system is often not accessible through IE browsers on other machines. In fact, the tested machine is still alive, but the service on the machine feels a bit unsustainable. It is generally caused by unreasonable application server parameters or database connection settings.

(3) Error-27728: Step download timeout (120 seconds

Timeout, which is often proposed on the Internet, is divided into three parts: connect,receive and download. The default is 120s, but often we need to set it larger. The specific setting method is: Vugen-- "Vuser---" Runtime-settings---- "Preferences-" option, change the default value of Step download timeout (sec) 120s to the value you need, and then change HTTP-reguest connnect timeout (sec) and HTTP-reguest receive timeout (sec).

Is also the corresponding value.

Analysis of the reason: I think this change is a temporary cure (to cover up the exposed problems), and I can even think that it is a test method to cover up the ears and steal the bell.

Because in general, 120 seconds timeout is often used in stress testing, which under normal circumstances can explain the performance problem. However, many testers are not confident and believe in the authority of some so-called experts on the Internet to modify this parameter or that parameter.

Analyze the reasons: the picture on the page is too large; the deadlock in the database; program problems (for example, the page contains a large number of complex calculations, queries-- not reflected in the case of a single user, but in the case of multiple users can expose the problem) and so on may cause the problem.

The cause needs to be further analyzed, but testers should record this phenomenon in the test results report.

For more testing articles, see my blog: http://blog.sina.com.cn/jcy77

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.