Analysis of Common Test results of LoadRunner

During the test, the following common test situations may occur:

When the curve of transaction response time starts to rise slowly, then balances out, and finally falls slowly, this situation indicates that:

* From the graph of transaction response time, the continuous rise indicates that the processing capacity of the system is decreasing, and the response time of transactions becomes longer.

* Continuous balance indicates that the number of concurrent users reaches a certain number, and it may not be accepted at most. If there are more requests, wait;

* When the response time of transactions decreases, it indicates that the number of concurrent users is slowly decreasing, and the number of requests for transactions is also decreasing.

If the system doesn't have this drop-down mechanism, the response time gets longer and longer until the system crashes.

From the above analysis, it can be found that it is caused by the following reasons:

1. There is no limit on the number of users connected in the program, resulting in an increasing number of requests and a longer response time;

2. Memory leaks;

Second, CPU usage is rising, memory usage is also rising, everything else is normal;

Indicates resource contention that may occur in the system;

Cause:

Developers pay attention to resource allocation issues.

Third, all transaction response time, CPU, etc. are normal, and the business fails;

Cause:

Database may be locked, that is, you are operating a table or a record, others can not use, that is, the existence of mutual exclusion of data;

When the amount of data is large, there will be data confusion.