Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: dashboard QPS计算疑问
[TiDB Usage Environment] Production Environment
[TiDB Version] 5.2.1
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
Why does the TiDB dashboard only display QPS and not TPS metrics? I think the business is more concerned about the database’s TPS processing capability.
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
In TiDB Dashboard, only QPS is displayed at the top instead of the TPS metric because QPS better reflects the load and performance bottlenecks of the TiDB cluster.
QPS (Queries Per Second) refers to the number of query requests processed per second and is one of the important metrics for measuring database performance. In TiDB, QPS is influenced by multiple factors, including hardware configuration, network bandwidth, SQL statement complexity, index usage, etc. By monitoring QPS, the load and performance bottlenecks of the TiDB cluster can be promptly identified for optimization and adjustment.
In contrast, TPS (Transactions Per Second) refers to the number of transactions processed per second and is a metric for measuring the database’s transaction processing capability. In TiDB, TPS is influenced by multiple factors, including hardware configuration, network bandwidth, transaction complexity, lock contention, etc. Although TPS is also an important metric, due to the complexity and diversity of transaction processing in TiDB, monitoring and optimizing TPS is relatively more difficult. Therefore, TPS is not given a prominent position in TiDB Dashboard.
Okay, thank you for the response.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: TiDBer_pkQ5q1l0
|
username: 
|
username: