Skip to main content

Performance Data

Starting from TDengine 3.0, a built-in database performance_schema is provided, which stores performance-related statistical data. This section details the tables and table structures within it.

PERF_APP

Provides information about the applications (clients) accessing the cluster. You can also use SHOW APPS to query this information.

#Column NameData TypeDescription
1app_idUBIGINTClient ID
2ipBINARY(16)Client address
3pidINTClient process number
4nameBINARY(24)Client name
5start_timeTIMESTAMPClient start time
6insert_reqUBIGINTNumber of insert requests
7insert_rowUBIGINTNumber of rows inserted
8insert_timeUBIGINTProcessing time for insert requests, in microseconds
9insert_bytesUBIGINTByte size of insert request messages
10fetch_bytesUBIGINTByte size of query results
11query_timeUBIGINTQuery request processing time
12slow_queryUBIGINTNumber of slow queries (processing time >= 3 seconds)
13total_reqUBIGINTTotal number of requests
14current_reqUBIGINTNumber of requests currently being processed
15last_accessTIMESTAMPLast update time

PERF_CONNECTIONS

Information related to the database connections. You can also use SHOW CONNECTIONS to query this information.

#Column NameData TypeDescription
1conn_idINTConnection ID
2userBINARY(24)Username
3appBINARY(24)Client name
4pidUINTProcess number of the client initiating this connection on its server or host
5end_pointBINARY(128)Client address
6login_timeTIMESTAMPLogin time
7last_accessTIMESTAMPLast update time

PERF_QUERIES

Provides information about the SQL statements that are currently being executed. You can also use SHOW QUERIES to query this information.

#Column NameData TypeDescription
1kill_idUBIGINTID used to stop the query
2query_idINTQuery ID
3conn_idUINTConnection ID
4appBINARY(24)App name
5pidINTProcess number of the app on its host
6userBINARY(24)Username
7end_pointBINARY(16)Client address
8create_timeTIMESTAMPCreation time
9exec_usecBIGINTExecution time
10stable_queryBOOLWhether it is a supertable query
11sub_numINTNumber of subqueries
12sub_statusBINARY(1000)Subquery status
13sqlBINARY(1024)SQL statement

PERF_CONSUMERS

#Column NameData TypeDescription
1consumer_idBIGINTUnique ID of the consumer
2consumer_groupBINARY(192)Consumer group
3client_idBINARY(192)User-defined string, displayed by specifying client_id when creating a consumer
4statusBINARY(20)Current status of the consumer. Consumer statuses include: ready (normally available), lost (connection lost), rebalancing (consumer's vgroup is being allocated), unknown (unknown status)
5topicsBINARY(204)Subscribed topics. If multiple topics are subscribed, they are displayed as multiple lines
6up_timeTIMESTAMPTime when first connected to taosd
7subscribe_timeTIMESTAMPTime when the last subscription was initiated
8rebalance_timeTIMESTAMPTime when the last rebalance was triggered

PERF_TRANS

#Column NameData TypeDescription
1idINTIdentifier of the ongoing transaction
2create_timeTIMESTAMPCreation time of the transaction
3stageBINARY(12)Current stage of the transaction, usually one of redoAction, undoAction, commit
4db1BINARY(64)Name of the first database that has a conflict with this transaction
5db2BINARY(64)Name of the second database that has a conflict with this transaction
6failed_timesINTTotal number of times the transaction has failed
7last_exec_timeTIMESTAMPLast execution time of the transaction
8last_action_infoBINARY(511)Detailed information about the last failed execution of the transaction

PERF_SMAS

#Column NameData TypeDescription
1sma_nameBINARY(192)Name of the time-range-wise sma (precomputed time dimension)
2create_timeTIMESTAMPCreation time of the sma
3stable_nameBINARY(192)Name of the supertable to which the sma belongs
4vgroup_idINTName of the vgroup dedicated to the sma