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.
Checking the Storage Overview
- Log in to the console.
 - Click 
 in the upper left corner and select a region and project. - Click 
 in the upper left corner, and under Databases, click Data Admin Service. - In the navigation pane, choose Intelligent O&M > Instance List.
    
    
Alternatively, on the Overview page, click Go to Intelligent O&M.
 - In the upper right corner of the Instance List page, search for instances by engine type, instance name, or instance IP.
 - Locate the target instance and click Details.
 - Click the Storage Analysis tab and check information in the Overview area.
    
    
- The following information is displayed:
      
- Storage usage
 - Available storage
 - Average daily increase in the last week
 - Disk space distribution
        
 
         - Data space: disk space occupied by user data
 - OpLog: disk space for storing oplogs
 - Other: disk space for storing metadata and temporary files generated by databases and the OS
 
 
 - If you are running out of storage, click Scale in the upper right corner.
 
 - The following information is displayed:
      
 
Viewing the Disk Space Change Trend
You can view the disk space change trend.
Tablespaces
It shows you tables with abnormal tablespace growth last day, 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.
 
   - 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 2 Viewing diagnosis details
      
Top Databases and Tables
By analyzing disk space allocation and identifying the top 50 databases and tables with the largest physical file sizes, you can optimize those experiencing high usage.
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).
 
   - 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 reserved special characters, including slashes (/) and #p#p, is not counted.
 - Currently, only RDS for MySQL 5.7 and 8.0 are supported.
 - If your instance's memory usage is greater than 85% or it has more than 50,000 tables, DAS will not collect related information. This prevents performance slowdowns caused by collecting statistics on too many databases and tables.
 - Some statistics may be missing because of database or table data fluctuations.
 
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot