Author: gnuhpc
Source: http://www.cnblogs.com/gnuhpc/
TPS: the number of transactions processed by the transaction per second server per second.
Transactions per second (number of transactions processed per second), that is, the number of transactions processed by the server per second. It is the unit of measurement for the software test results. A transaction refers to the process in which a client sends a request to the server and then the server responds. The client starts timing when sending the request and ends timing after receiving the server response. This is used to calculate the time used and the number of completed transactions, and finally uses this information to estimate the score. The client uses the weighted covariance function average method to calculate the client's score. The test software uses the client's information to calculate the overall TPS score of the server using the weighted covariance function average method.
TPS includes one incoming message and one outgoing message, plus one user database access. (Service TPS = caps × average TPS of each call)
Online PV is a parameter of great interest to performance testing, architecture, development, and operation personnel;
In performance testing, PV is represented by TPS. The conversion formula is as follows:
TPS average = (Pv * 80%)/(24*60*60 * 40%)/number of servers = PV/s
TPS peak value = (Pv * 80%)/(24*60*60 * 40%) * 1.6)/Server COUNT = PV/s
Generally, the evaluation system performance is measured by the number of technical transactions completed per second. The overall processing capability of the system depends on the TPS value of the minimum processing capacity module. Based on experience, the processing capability of the application system is generally about 10. TPS varies greatly from application system to application system. Generally, the results of performance testing must be accurately estimated.
Author: gnuhpc
Source: http://www.cnblogs.com/gnuhpc/