Important

The SingleStore 9.1 release candidate (RC) gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 9.1.

MV_ACTIVITIES_EXTENDED

This view provides a detailed profile of all tasks which ran recently on any node in the cluster.

It holds a row per activity. Each row describes the instances of its activity which ran during a recent interval of time. It reports the sum of the profiling statistics of each task in the set, as collected over the recent interval. Activities can include tasks such as garbage collection and backups, in addition to queries.

mv_activities determines recent resource use by computing the change in MV_ACTIVITIES_EXTENDED_CUMULATIVE over an interval of time. This interval is controlled by the value of the activities_delta_sleep_s session variable.

MV_ACTIVITIES_EXTENDED may only be queried while connected to an aggregator node.

SingleStore recommends using this view to get fine-grained understanding of the system behavior described in mv_activities. The main distinctions between mv_activities and MV_ACTIVITIES_EXTENDED are:

For most queries, MV_ACTIVITIES_EXTENDED will report the resource usage of the query with at least a row per partition.
MV_ACTIVITIES aggregates these into a single row per query.
MV_ACTIVITIES reports simplified statistics, while MV_ACTIVITIES_EXTENDED reports extended statistics.

However, SingleStore recommends against the use of MV_ACTIVITIES_EXTENDED to compute the average latency or resource usage of a query. This is because its statistics include the latency and resource usage of currently running tasks, which will skew attempted average calculations. SingleStore recommends mv_finished_tasks for this purpose instead.

Column name	Description
`NODE_ID`	An `id` equal to `id` in the row of `mv_nodes` describing the node on which the instances ran.
`ACTIVITY_TYPE`	The type of the activity.
`ACTIVITY_NAME`	The name of the activity. This column is often human-readable, but does not include the full query text for query tasks. Join with `mv_queries` for the query text.
`AGGREGATOR_ACTIVITY_NAME`	The aggregator activity name of the activity.
`DATABASE_NAME`	The name of the database associated with the activity, or `NULL` if none could be assigned.
`PARTITION_ID`	The unique ID of the database partition associated with the activity, or `NULL` if none could be assigned.
`RUN_COUNT`	The number of instances which were running at the end of the interval.
`SUCCESS_COUNT`	The number of instances which completed successfully during the interval.
`FAILURE_COUNT`	The number of instances which completed unsuccessfully during the interval.
`ACTIVITY_TRACKING_ID`	An ID that can be used to identify the activities associated with a session. Configure the `activity_tracking_id` session engine variable to specify an ID for all the activities associated with the queries run in the current session. In the case of pipeline queries, this value is set automatically in the following way: If the queries are directly run by the pipeline, their `activity_tracking_id` is `PI_<PIPELINE_ID>`. If the pipeline calls a stored procedure, the `activity_tracking_id` of the queries run by this stored procedure is set as `PR_PI_<PIPELINE_ID>`.
EXTENDED STATISTICS	This view contains all extended statistics columns, including: `cpu_time_ms`, `cpu_wait_time_ms`, `disk_logical_read_b`, `disk_logical_write_b`, `disk_physical_read_b`, `disk_physical_write_b`, `disk_time_ms`, `elapsed_time_ms`, `lock_row_time_ms`, `lock_time_ms`, `log_buffer_b`, `log_buffer_time_ms`, `log_flush_time_ms`, `memory_bs`, `memory_major_faults`, `network_logical_recv_b`, `network_logical_send_b`, and `network_time_ms`.

MV_ACTIVITIES_EXTENDED

Was this article helpful?

Was this article helpful?