On this page
Starting in version 5.
One of the core responsibilities of a database administrator is to monitor the performance of a database, and as necessary, take preventative or reactive steps to maintain its health.
To help alleviate these difficulties, SingleStoreDB gathers statistics about the entire cluster, including all queries across all nodes, and exposes them in logical tables (views).
Which queries are using the highest proportion of system resources?
Is a query running, or is it waiting for available resources?
Which system resources are causing bottlenecks?
Using these views in conjunction with built-in commands such as
PROFILE, an administrator can better diagnose the root cause of pathological query performance, and determine which workload or resource improvements are necessary.
You can enable the advanced counters by setting the
read_ global variable, which is discussed in the Advanced Statistics section of the Management Statistics Reference topic.
For more information on how to set engine variables, see the Engine Variables topic.
SET GLOBAL read_advanced_counters = ON;
Query OK, 0 rows affected (0.00 sec)
Each management view – and the type of data stored in it – is intended for performance analysis methodologies which seek to accomplish the following goals:
Finding high-latency queries
Finding the bottlenecks causing high-latency queries
Gathering statistics about all aspects of cluster performance to find issues beyond query execution
Management views make it easier to achieve these goals by exposing the appropriate performance counters to measure each relevant attribute of the database, namely:
Node-level statistics, including what queries are running on both aggregators and leaves, or which background tasks are consuming resources
Database-level and partition-level statistics, including the specific database partition(s) associated with a query
Query-level statistics, including latency, throughput, saturation, and error metrics
Together, these statistics provide insight into both high-level and low-level activities on the cluster.
Refer Diagnosing a Performance Issue Using Workload Profiling for use cases and scenarios.
Last modified: January 20, 2023