MV_ ACTIVITIES
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 high-level summary profile of all tasks which ran recently on any node in the cluster.
It holds a row per high-level activity H.
The effect of grouping the instances of multiple activities together is mainly to group all tasks associated with a query, across all partitions, into a single row.
mv_
determines recent resource use by computing the change in mv_
over an interval of time.activities_
session variable.
mv_
may only be queried while connected to an aggregator node.
SingleStore recommends using this view to begin a performance investigation, as it is the most concise.
However, SingleStore recommends against the use of mv_
to compute the average latency or resource usage of a query.mv_
for this purpose instead.
Column name |
Description |
---|---|
|
The type of the high-level activity. |
|
The name of the high-level activity. |
|
The name of the database associated with the activity, or |
|
The number of instances which were running at the end of the interval. |
|
The number of instances which completed successfully during the interval. For multi inserts ( |
|
The number of instances which completed unsuccessfully during the interval. |
This view contains all simplified statistics columns, including: |
|
|
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: April 28, 2025