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_MEMORY_USAGE

Column Name	Description
`NODE_ID`	The unique ID of a given node.
`ALLOC_BYTES`	The memory usage in bytes.
`ALLOC_PROFILE`	The memory allocation type. `Total_<category>_memory` indicates the total memory usage in `<category>`. `Buffer_Manager_<category>` indicates the total memory used by the buffer manager in `<category>`. Memory usage options include: `Linux_resident_memory`, `Linux_resident_shared_memory`, `Malloc_active_memory`, `Malloc`, `Total_server_memory`, `Total_table_memory`, and additional options that provide fine-grained detail for in-depth investigations.
`OWNER`	A JSON object identifying the structure that holds the memory. For a database table, the JSON is similar to: JSON {"DATABASE":"XDB_0","TABLE":"Xtab1"} For a process, the JSON is similar to: JSON {"ACTIVITY":"Select_profile_symbols__MV_MEMORY_USAGE__et_al_36da08f893abf492", "ACTIVITY_TRACKING_ID":null, "AGGREGATOR_ACTIVITY":"Select_profile_symbols__MV_MEMORY_USAGE__et_al_36da08f893abf492", "DATABASE":"information_schema", "RAW_TASK":"information_schema", "THREAD_ID":1159312,"TYPE":"Query"}
`OWNER_TYPE`	The type of the owner. Options include: `SERVER`: Owned by the engine. `ALLOCATOR`: Owned by an allocator. `RG_POOL`: Owned by the resource group pool. `USER_TABLE`, `INTERNAL_TABLE`, `TEMP_TABLE`: Owned by a user table, system table, or temp table. `PROCESS`: Owned by an active process. `TRANSACTION`: Owned by a transaction.
`GROUP_ID`	A unique identifier (ID) assigned to a memory usage group. This ID does not have a specific meaning. It is a unique identifier only.
`SUBGROUP_IDS`	A JSON object that includes one or more subgroup IDs. Use the subgroup IDs to obtain a breakdown of the memory usage for group `GROUP_ID` and `ALLOC_PROFILE`.
`AGGREGATE_COUNT`	If the row was aggregated, the number of aggregated rows. Otherwise 1. A value of `<others>` in `OWNER` indicates the value is an aggregated value.

Remarks

Important

It is acceptable to aggregate memory groups (ALLOC_PROFILE options) with the same ID. Do not aggregate across different groups. Aggregating across different groups results in double counting.

ALLOC_PROFILE

The memory used by different ALLOC_PROFILE options is not mutually exclusive and is not additive.

For example, the ALLOC_PROFILE option Buffer_memory_for_table shows the memory used for each table in the system and includes both the memory used by the rowstore and the in-memory portion of the columnstore. Memory usage can also be displayed by allocation type such as Buffer_tracked_regular or Buffer_not_tracked. Thus, a particular piece of memory may be counted both in Buffer_memory_for_table and Buffer_tracked_regular.

OWNER

When OWNER is <others>, this indicates that the engine has aggregated values displayed in this row to minimize the number of rows output.

Use the information in the OWNER column to join with MV_TASKS or MV_ACTIVITIES.

Security

The PROCESS_ACL and SHOW_METADATA_ACL permissions are required to see the content of this view.