All Products
Search
Document Center

AnalyticDB:Instance resource configuration

Last Updated:Jun 05, 2026

Instances of AnalyticDB for PostgreSQL in serverless automatic scheduling mode automatically pause and resume based on traffic. You can configure a serverless automatic scheduling instance's Computing Resource Threshold and Wait Time for Idle Resource Release to reduce costs. If an instance has no traffic for a specified period, it automatically enters the idle state. You are not charged for compute resources while the instance is in the idle state.

Prerequisites

The instance is in serverless automatic scheduling mode.

Note

The autoscaling feature for AnalyticDB for PostgreSQL of AnalyticDB for PostgreSQL is in invitational preview. To use this feature, submit a ticket to apply.

Procedure

  1. Log on to the AnalyticDB for PostgreSQL console.
  2. In the upper-left corner of the console, select a region.
  3. Find the target instance and click Change Configuration in the Actions column.

  4. On the Instance Resource Configuration page, click Edit.

  5. Set the Computing Resource Threshold and Wait Time for Idle Resource Release, and then click OK.

    • Computing Resource Threshold: An integer from 8 to 32 in increments of 8. The unit is ACU.

    • Wait Time for Idle Resource Release: The number of seconds of inactivity before the instance enters the Idle state. The minimum value is 60 seconds.

  6. In the Are you sure that you want to perform this operation? dialog box, click OK.

    Note

    The new configuration takes effect in 2 minutes.

Related API

API

Description

ModifyDBInstanceConfig

Modifies the computing resource threshold and wait time for idle resource release for an instance in serverless automatic scheduling mode.

Related documents

  • For more information about serverless mode for AnalyticDB for PostgreSQL, see Serverless mode.

  • If your instance is in elastic storage mode or serverless manual scheduling mode, you can manually pause and resume the instance. For more information, see Manually pause and resume an instance.