Performance Insight is a Database Autonomy Service (DAS) feature that charts key performance metrics and session activity to help you identify the root causes of database performance issues.
DAS also offers a new version of Performance Insight that adds SQL-level aggregation based on Performance Schema data, including Resource Usage, Executions, Scanned Rows, and Execution Duration, plus throttling and optimization for specific SQL statements. For details, see Performance insight (new version).
Supported database types
Performance Insight (original version) supports the following database instance types:
ApsaraDB RDS for MySQL
ApsaraDB MyBase for MySQL
ApsaraDB RDS for PostgreSQL
PolarDB for MySQL
PolarDB for PostgreSQL
PolarDB for PostgreSQL (Compatible with Oracle)
How it works
Performance Insight collects data from two sources, depending on whether Performance Schema is enabled on your instance:
Performance Schema enabled — data is collected from Performance Schema.
Performance Schema disabled — data is collected from active sessions.
The Average Active Session (AAS) chart is the core diagnostic view. AAS measures how many sessions are concurrently active on your database at any given point in time. A sustained spike in AAS signals elevated database load. Cross-referencing that spike against SQL activity reveals which queries are driving it.
Enable Performance Insight
Log on to the DAS console.
In the left-side navigation pane, click Instance Monitoring.
Find the database instance you want to manage and click its instance ID.
In the left-side navigation pane, click Performance Insight.
On the Performance Insight tab, click Enable Performance Insight, then click OK in the confirmation dialog.
If your instance is ApsaraDB RDS for MySQL or PolarDB for MySQL, click Back to Previous Version to enable the original version.
To disable Performance Insight, click Disable Performance Insight on the Performance Insight tab.
Diagnose performance issues
View performance metrics
In the Performance Insight section, set a time range and click Search.
Keep the following data availability limits in mind:
Section Available data range Performance Insight Up to 7 days within the last month Average Active Session Last 3 days The end time must be later than the start time.
To inspect a specific metric in detail, click Details to the right of the metric name — for example, Memory Usage/CPU Utilization.
Identify the root cause
Use the following workflow to trace a performance issue to the specific SQL statements causing it:
Check the Average Active Session chart for spikes. A sustained spike indicates elevated database load.
In the Average Active Session section, review the session trend dimensions to identify which session types account for the spike.
Switch to the SQL tab to see which SQL statements were active during the high-load period.
Click Optimize in the Actions column for a specific SQL statement to open the SQL Diagnosis Optimization page. Review the SQL statement, its execution plan, and the diagnosis result.
What's next
Performance insight (new version) — upgrade to the new version for SQL-level aggregation, throttling, and optimization.