All Products
Search
Document Center

AnalyticDB:View and analyze cluster and table data size

Last Updated:Mar 30, 2026

The Storage Overview page shows how much storage your AnalyticDB for MySQL cluster uses — from the overall cluster size down to individual tables — so you can identify storage hotspots and act before disk usage becomes a problem.

View cluster-level storage metrics

The Storage Overview section shows total, hot, and cold data sizes for the cluster, along with data growth rates.

  1. Log on to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left-side navigation pane, click Clusters. On the Clusters page, find the target cluster and click its cluster ID.

  2. In the left-side navigation pane, choose Storage Analysis > Storage Overview.

  3. In the Storage Overview section, review the following metrics.

Top-level size metrics

Metric Description
Total Data Size Total data size of all tables in the cluster.
Hot Data Size Hot data size of all tables in the cluster. For more information, see Hot and cold data separation.
Cold Data Size Cold data size of all tables in the cluster. For more information, see Hot and cold data separation.
Note

Data Warehouse Edition (Reserved Mode) clusters do not support hot and cold data separation, so the cold data size is not displayed for these clusters.

Data growth metrics

Metric Description
Last 24 Hours Growth of total cluster data size over the last 24 hours. Formula: Data growth in the last 24 hours = Data size at the current point in time − Data size 24 hours ago.
Daily Last Week Average daily growth of total cluster data size over the last week. Formula: Daily average growth over the last week = (Data size at the current point in time − Data size at the same point in time 7 days ago) / 7.

Hot data size breakdown

Each partition's total data size is categorized into four types. The following table covers the breakdown for hot partitions. The cold data breakdown follows the same four categories, applied to cold partitions.

Data type Description
Table Record Data size of hot partitions in all tables, excluding regular index and primary key index data.
Regular Index Data size of regular indexes in hot partitions. A full-column index is created by default when you create a table. If regular index data is large, delete unused indexes to reduce storage. See Schema optimization.
Primary Key Index Data size of primary key indexes in hot partitions. If this value is large, find the table with a high primary key index ratio in the Table Storage Information section and optimize accordingly.
Other Size of metadata, temporary data, and other data in hot partitions.

View node-level disk usage trends

The Storage Trend section shows how data size and disk usage change over time at the node level, helping you catch gradual growth and unexpected spikes.

  1. Log on to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left-side navigation pane, click Clusters. On the Clusters page, find the target cluster and click its cluster ID.

  2. In the left-side navigation pane, choose Storage Analysis > Storage Overview.

  3. In the Storage Trend section, select a time range from the drop-down list on the right, or drag the time cursor below the Total Data Size and Node Disk Usage charts.

Important

The maximum historical range is 30 days. Each query can cover at most 7 days.

The metrics available in the Storage Trend section differ by cluster type.

Data Warehouse Edition (Elastic Mode), Enterprise Edition, Basic Edition, and Data Lakehouse Edition

Category Metric Description
Total Data Size Average Hot Data Size of Storage Nodes Average hot data size across all data nodes in the cluster.
Maximum Hot Data Size of Storage Nodes Maximum hot data size among all data nodes in the cluster.
Hot Data Size Hot data size of all tables in the cluster.
Cold Data Size Cold data size of all tables in the cluster.
Node Disk Usage Average Disk Usage Average disk usage across all data nodes in the cluster.
Maximum Disk Usage Maximum disk usage among all data nodes. Formula: Maximum disk usage = Storage space occupied by the node with the most data / (Maximum hot data size of an elastic I/O unit (EIU) / 0.9) × 100%. The hot data size limit per elastic I/O unit (EIU) is 8 TB (use 8,000 GB in calculations). For example, if the hot data size of a node is 8,000 GB, the maximum disk usage is 8,000 / (8,000 / 0.9) × 100% = 90%.
Disk Usage Threshold (90%) The cluster lock threshold. If maximum disk usage exceeds 90%, the cluster is locked: reads still work, but writes are blocked.

Recommended: Set a disk usage alert at 80% in Cloud Monitor so you can act before the cluster is locked. See Create an alert rule.

Data Warehouse Edition (Reserved Mode)

Category Metric Description
Total Data Size Total Data Size Total data size of all tables in the cluster.
Average Data Size of Storage Nodes Average data size across all data nodes in the cluster.
Maximum Data Size of Storage Nodes Maximum data size among all data nodes in the cluster.
Node Disk Usage Average Node Disk Usage Average disk usage across all data nodes in the cluster.
Maximum Disk Usage of Node Maximum disk usage among all data nodes. Formula: Maximum disk usage = (Storage space occupied by the node group with the most data / Storage space of a single node group) × 100%. For example, if you have two node groups of 200 GB each, and data is distributed as 60 GB in one and 80 GB in the other, the maximum disk usage is (80 / 200) × 100% = 40%.
Disk Usage Threshold (90%) The cluster lock threshold. If maximum disk usage exceeds 90%, the cluster is locked: reads still work, but writes are blocked.

Recommended: Set a disk usage alert at 80% in Cloud Monitor so you can act before the cluster is locked. See Create an alert rule.

View table-level storage details

The Table Storage Information section lists storage metrics for each table. Use it to identify which tables consume the most space and whether index overhead is a contributing factor.

  1. Log on to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left-side navigation pane, click Clusters. On the Clusters page, find the target cluster and click its cluster ID.

  2. In the left-side navigation pane, choose Storage Analysis > Storage Overview.

  3. In the Table Storage Information section, review the metrics for each table.

Metric Description
Database Name of the database.
Table Name Name of the table.
Storage Percentage Share of the cluster's total data size that this table occupies. Formula: Storage percentage = (Total data size of the table / Total data size of the cluster) × 100%.
Total Data Size Total data size of the table, calculated using either of these equivalent methods. Method 1: Hot Data Size + Cold Data Size. Method 2: Table Record + Regular Index + Primary Key Index + Other.
Hot Data Size Data size of all hot partitions in the table, including Table Record, Regular Index, Primary Key Index, and Other data.
Cold Data Size Data size of all cold partitions in the table, including Table Record, Regular Index, Primary Key Index, and Other data.
Table Record Data size of all partitions in the table, excluding regular index and primary key index data.
Regular Index Data size of regular indexes across all partitions. If this value is disproportionately large relative to Table Record, consider deleting unused indexes. See Schema optimization.
Primary Key Index Data size of the primary key index across all partitions.
Other Size of metadata and temporary data across all partitions.
Table Rows Number of rows in the table.
Partitions Number of partitions in the table.

API reference

API operation Description
DescribeDBClusterSpaceSummary Queries the storage overview of an Enterprise Edition, Basic Edition, or Data Lakehouse Edition cluster.
DescribeDBClusterSpaceSummary Queries the storage overview of a Data Warehouse Edition cluster.
DescribeTableStatistics Queries table statistics for a Data Warehouse Edition cluster.
DescribeDBClusterPerformance Queries performance data for a Data Warehouse Edition cluster.

What's next