This document is a "software performance testing LoadRunner combat the study notes" summary
The first part of the article thought
1, performance testing parameters
1) The client response time
Response time = CT + (N1 + N2 + N3) + (N4 + N5 + N6) + WT + AT + DT
CT: Client Time. For thin clients can be ignored, for fat client (such as Ajax, html5 + AngularJS + Bootstrap), due to the large number of client embedded processing logic consumes a long time may need attention
Network response time: can be divided into 2 parts
- (N1 + N2 + N3): client request network delay
- (N4 + N5 + N6): web server response delay
Server response time: server capacity can be measured, is generally divided into three parts:
--WT：Web Server Time
--AT：App Server Time
--DT：Database Time
2) the number of concurrent
System users: the system understood as the total number of registered users
Online users: total number of users currently accessing
Number of concurrent users: Let the same time the number of users the server generates pressure
3) Throughput
Throughput: refers to the amount of data transmission on an integrated network in a performance testing. "Swallowed" into a request, "spit out" is the result
Throughput: amount of data transmitted on the network per unit time
4) TPS (Transaction Per Second) by the number of transactions per second
Number of transaction or transactions per second can handle. It is an important indicator
5) Click per second