Help Center/ Data Admin Service/ User Guide/ MySQL/ Intelligent O&M (New Version)/ Storage Analysis
Updated on 2024-11-28 GMT+08:00
View PDF
Share

Storage Analysis

Storage occupied by data and logs and historical changes of storage usage are important for database performance. The Storage Analysis page displays storage overview and disk space distribution of your instance. In addition, DAS can estimate the available days of your storage based on historical data and intelligent algorithms, so that you can scale up storage in a timely manner. Auto Scale, Tablespaces, Top 50 Databases, and Top 50 Tables are also available on this page.

Viewing Storage Space Usage

  1. Log in to the DAS console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner, and under Databases, click Data Admin Service.
  4. In the navigation pane, choose Intelligent O&M > Instance List.

    Alternatively, on the Overview page, click Go to Intelligent O&M.

  5. In the upper right corner of the Instance List page, search for instances by engine type, instance name, or instance IP.

    Figure 1 Searching for instances

  6. Locate the box containing your target instance and click Details.
  7. Choose Storage Analysis. In the Overview area, view the space usage.

    Figure 2 Overview
    • The following information is displayed:
      • Storage usage
      • Available and total storage
      • Average daily increase in last week
      • Available days of storage

        If the average daily increase in last week is 0 GB, the estimated available days of storage are unlimited and are not displayed.

    • If the space is insufficient, click Scale in the upper right corner.
    • You can also enable Autoscaling. If available storage drops to or below 10 GB or 10%, total storage will automatically be scaled up by 15%. If the increased storage is not a multiple of 10 GB, the system rounds it up to the nearest multiple of 10. If your account balance is insufficient, autoscaling will fail.

      Autoscaling is not available to free instances. To use the function, set free instances as paid instances or subscribe to Intelligent O&M.

Tablespaces

This function helps you diagnose exceptions of tables, for example, counting tables with abnormal tablespace growth, tables without primary keys, and tables without indexes.

Both automatic diagnosis and manual diagnosis are supported.

  • Tablespaces function is not available to free instances. To use the function, set free instances as paid instances or subscribe to Intelligent O&M.
  • If the number of tables exceeds 5,000, manual diagnosis cannot be used.
  • If the CPU usage exceeds 90%, manual diagnosis cannot be used.
  • Tables in the Top 50 Tables are automatically diagnosed. Scope for manual table diagnosis is not limited.
In the Tablespaces area, you can view tablespace diagnosis information.
Figure 3 Tablespaces
  • Auto Diagnosis

    The system automatically diagnoses tables at about 04:00 every day.

    In the left part of the Tablespaces area, you can view tables whose tablespace has grown abnormally in the past day. You can click the number to view the diagnosis details.

    Any table whose tablespace has grown by more than 10,240 MB in the past day is counted. You can also click on the right of Auto Diagnosis to set the upper limit for daily tablespace increase.

  • Manual Diagnosis

    Click Re-diagnose to manually trigger a diagnosis task. This operation can only be performed once every 5 minutes.

    After the diagnosis is successful, you can view the number of tables without primary keys and indexes. You can click a number to view the diagnosis details.

    Figure 4 Viewing diagnosis details

Viewing Disk Space Distribution

You can view the distribution and change trend of the storage space.

Figure 5 Viewing disk space distribution

If the total number of files in your disk space (including data space, binlog space, slow query log space, relay log space, audit log space, temporary space, and other space) exceeds 10,000, information about the files or display disk space distribution and usages over time will not be collected on the console. This prevents performance slowdowns caused by collecting statistics on too many files. If this happens, contact technical support.

  • Data space: Disk space occupied by user data
  • Binlog: Disk space occupied by binlogs
  • Slow query log: Disk space occupied by slow logs
  • Relay log: Disk space occupied by relay logs
  • Audit log: Disk space occupied by audit logs
  • Temporary space: Disk space occupied by temporary files
  • Other: Disk space reserved by the operating system for system users. About 5% of the disk space is reserved in Linux.

Top Databases and Tables by Physical File Size

You can view the top 50 databases and tables by physical file size and identify the databases and tables with high usage based on storage space distribution.

Figure 6 Viewing top 50 databases and tables

Click View Chart to view data volume changes in the last 7 days, last 30 days, or a custom time period (spanning no more than 30 days).

Figure 7 Viewing a trend chart
  • DAS collects data at about 04:00 every day.
  • Physical file sizes are precisely recorded, but other fields' values are estimated. If there is a large gap between a file size and another field, run ANALYZE TABLE on the table.
  • A database or table whose name contains special characters, including slashes (/) and #p#p, is not counted.
  • Top databases and tables are available only in RDS for MySQL 5.7 and 8.0.
  • If there are more than 50,000 tables in your instance, to prevent data collection from affecting the instance performance, top databases and tables will not be counted.
  • Some statistics may be missing because data of database or tables is fluctuating.