Qps:queries per Second query amount/Second, is a server per second can be the corresponding number of queries, is a specific query server in the specified time the amount of queries processed by the measure of how much.
Tps:transactions per Second is the number of transactions per second, which is the number of transactions that a database server processes within a unit of time.
Many of the data on the QPS TPS algorithm are
Questions = Show global status like ' queries ';
Uptime = Show global status like ' uptime ';
Qps=queries/uptime
Com_commit = Show global status like ' Com_commit ';
Com_rollback = Show global status like ' Com_rollback ';
Uptime = Show global status like ' uptime ';
tps= (Com_commit + com_rollback)/uptime
But this place if the uptime infinity, the machine can not be at all times at full load under the work, the resulting value may become meaningless:
For tps= (Com_commit+com_rollback)/uptime
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5C/15/wKioL1Uad82xcUfXAAIPoMddYHs644.jpg "title=" 1.png " alt= "Wkiol1uad82xcufxaaipomddyhs644.jpg"/>
So the TPS and the QPS in this place. I should say this: for a period of time, use the Mysqladmin extended-status, and then calculate the difference between the QPS TPS per second in a period of time, or the average of 10 seconds per second!
That is: in a certain period of time my library of the QPS generally run to how much, or the highest number!
This article is from the "husband's minister" blog, please be sure to keep this source http://fucheng.blog.51cto.com/2404495/1627039
MySQL QPS TPS