Performance Tracing Tool

Note: TRACING ON/OFF hasn't been supported yet.

IoTDB supports the use of the TRACING clause to enable performance tracing of executed statements. Users can use the performance tracing tool to analyze potential performance problems in some statements.

Traceable statement: SELECT only.

The current performance analysis includes the following contents:

1. The elapsed time of each stage of the execution process.
2. Statistics related to performance analysis. For query statements, it includes the number of time series queried, the number of Tsfile files accessed, the total number of chunks to be scanned, and the average number of data points contained in the chunk, the total number of pages read, and the number of overlapped pages.

Example

For example, execute tracing select * from root, will display the following contents:

Tracing Activties:
+------------------------------------------------------+------------+
|                                              Activity|Elapsed Time|
+------------------------------------------------------+------------+
|Start to execute statement: tracing select * from root|           0|
|                            Parse SQL to physical plan|           4|
|                              Create and cache dataset|          16|
|                              * Num of series paths: 3|            |
|                       * Num of sequence files read: 2|            |
|                     * Num of unsequence files read: 1|            |
|        * Num of sequence chunks: 6, avg points: 100.0|            |
|      * Num of unsequence chunks: 3, avg points: 100.0|            |
|         * Num of Pages: 9, overlapped pages: 0 (0.0%)|            |
|                                      Request complete|          20|
+------------------------------------------------------+------------+