MV_ QUERY_ ACTIVITIES_ EXTENDED_ CUMULATIVE
Warning
SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.
This view provides a detailed profile of completed and currently running queries on all nodes of the cluster.
Column name |
Description |
---|---|
|
An ID equal to |
|
An ID shared by all instances of the activity. |
|
The |
|
The de-parameterized text of the query. |
|
The aggregator query text. |
|
The name of the database associated with the query, or |
|
The unique ID of the database partition associated with the query, or |
|
Milliseconds spent running on a CPU. |
|
Milliseconds spent waiting for a CPU to become available. |
|
Wall clock milliseconds elapsed during execution. |
|
Milliseconds spent waiting on table row locks. |
|
Milliseconds spent waiting on locks and condition variables, excluding row locks. |
|
Milliseconds spent waiting for physical disk I/O to complete. |
|
Milliseconds spent waiting for sockets to be ready to send or receive data. |
|
Milliseconds spent waiting for space in the transaction log buffer. |
|
Milliseconds spent waiting for transaction log records to be flushed to disk. |
|
Bytes received from a socket. |
|
Bytes written to a socket. |
|
Bytes read from the filesystem. |
|
Bytes written to the filesystem. |
|
Bytes actually read from physical disk. |
|
Bytes actually written to physical disk. |
|
|
|
Number of page faults which required disk I/O to resolve. |
|
The amount of time, in seconds, that the pipeline spent waiting on the extractor to complete its operation. |
|
The amount of time, in seconds, that the pipeline spent waiting on the transform to complete its operation. |
|
The number of instances which were running at the end of the interval (since the plan was generated). |
|
The number of instances which completed successfully during the interval (since the plan was generated). |
|
The number of instances which completed unsuccessfully during the interval (since the plan was generated). |
|
The number of warnings generated during query execution. |
|
High-level information about the plan, including warnings/errors, etc. |
|
A query sometimes cannot find its input data in blob cache, referred to as a cache miss. |
|
The time (milliseconds) that were spent on waiting for blob cache data. |
Last modified: January 25, 2024