In Serverless automatic scheduling mode, AnalyticDB for PostgreSQL monitors service traffic and automatically starts or stops based on detected activity. Configuring the Computing Resource Threshold and Wait Time for Idle Resource Release lets you control when the instance enters Idle status. No computing resource charges apply while the instance is idle.
How automatic scheduling works
When no service traffic is detected for the duration set in Wait Time for Idle Resource Release, the instance transitions to Idle status. While idle, computing resources are released and billing for computing resources stops.
The two parameters you configure control this behavior:
| Parameter | Description | Range |
|---|---|---|
| Computing Resource Threshold | The maximum computing resources allocated to the instance. | 8–32 AnalyticDB Compute Units (ACUs), in increments of 8 |
| Wait Time for Idle Resource Release | The period of inactivity before the instance transitions to Idle status — when this period elapses with no traffic detected, billing for computing resources stops. | Minimum: 60 seconds |
Configure instance resources
The instance must be in Serverless automatic scheduling mode before you begin.
Log on to the AnalyticDB for PostgreSQL console.
In the upper-left corner of the console, select a region.
Find the target instance and click Change Configuration in the Actions column.
On the Instance Resource Configuration page, click Edit.
Set Computing Resource Threshold and Wait Time for Idle Resource Release, then click OK.
In the Are You Sure You Want To Modify? dialog box, click Confirm.
API reference
| API | Description |
|---|---|
| ModifyDBInstanceConfig | Modifies the computing resource threshold and the wait time for idle resource release for an instance in Serverless automatic scheduling mode. |
Related topics
Serverless mode — learn more about how Serverless mode works.
Manually start and stop an instance — if your instance is in elastic storage mode or Serverless manual scheduling mode.