All Products
Search
Document Center

Serverless App Engine:Idle mode (invitational preview)

Last Updated:Aug 27, 2025

When Idle mode is enabled, the unit price for idle application instances is lower than for active application instances, which helps reduce costs.

Important
  • This feature is in invitational preview. To use this feature, contact our technical support team in the DingTalk group (ID: 32874633) to enable it.

  • Idle mode is supported only by the Standard and Professional editions of SAE applications.

Idle mode billing

When you enable Idle mode, the Compute Unit (CU) conversion coefficient for idle vCPUs is lower than that for active vCPUs. This applies to application instances that are in an idle status. For more information, see the following table.

Application version

Billable item

CU conversion coefficient for default servers

CU conversion coefficient for Hygon servers

Unit of conversion coefficient

Standard Edition

Active vCPU usage

1

1.274

CU per vCPU-second

Idle vCPU usage

0.2

0.2548

CU/(vCPU × second)

Professional Edition

Active vCPU usage

1.1

1.4014

CU/vCPU-second

Idle vCPU usage

0.22

0.28028

CU/vCPU-second

Enable Idle mode

  1. In the SAE application list, select a destination region and namespace at the top of the page. Then, click the Application ID of the target application to go to the application details page.

  2. On the Basic Information page, click the Auto Scaling tab. In the Idle Mode section, enable Idle mode.

    Important

    After you enable Idle mode, the system adjusts the application instances. This process may cause business interruptions. Therefore, before you enable Idle mode, ensure that you have configured measures such as setting graceful start and shutdown.

Conditions for an application instance to be in an idle status

  • The vCPU specification per instance must be <= 8 cores. There are no requirements for the memory specification.

    • For an instance with a vCPU specification <= 2 cores, the actual vCPU usage per instance must be < 0.03 cores.

    • For an instance with a vCPU specification > 2 cores and <= 8 cores, the actual vCPU usage per instance must be < (vCPU specification per instance) × 1%. For example, if the vCPU specification per instance = 4 cores, the actual vCPU usage per instance must be < 0.04 cores for the instance to be in an idle status.

  • The network traffic received per instance must be < 20,000 bytes/second. There are no requirements for outbound network traffic.

  • The duration that an instance is in the idle status must be <= 50% of its total runtime. The excess duration is billed as active.

View resource usage to check whether the idle conditions are met

After you enable Idle mode, you can view resource usage by the Application or Instance dimension to determine whether the idle conditions are met. You can view statistics for a specific time span or a custom time range.

  • Application: The number of application instances and the percentage of idle duration in the application's CPU resource usage (core × hour).

  • Instance: The idle status of the instance, the percentage of idle duration in the instance's CPU resource usage (core × hour), the CPU usage (cores), and the bytes received by the instance (B/s).

Disable Idle mode

  1. In the SAE application list, select a destination region and namespace at the top of the page. Then, click the Application ID of the application to go to the application details page.

  2. On the Basic Information page, click the Auto Scaling tab. In the Idle Mode section, disable Idle mode.

    Important

    After you disable Idle mode, application instances are billed as active instances.