Help Center/ TaurusDB/ User Guide/ Serverless Instances/ Enabling Dynamic Serverless for Instances with Fixed Specifications (OBT)
Updated on 2026-06-04 GMT+08:00
View PDF
Share

Enabling Dynamic Serverless for Instances with Fixed Specifications (OBT)

Scenarios

Enterprise IT systems often face two challenges of underutilized resources and cost inefficiencies caused by volatile workloads. For example, if you purchase a pay-per-use or yearly/monthly instance and the workload fluctuates greatly, resources may be wasted during off-peak hours or performance bottlenecks occur during spikes. To address these issues, TaurusDB supports Dynamic Serverless for both pay-per-use and yearly/monthly instances. You can set a custom compute capacity range. The system automatically adjusts compute capacity in response to workload fluctuations. This ensures flexible resource scheduling and reduces costs.

Supported Versions

The kernel version must be 2.0.54.240600 or later.

For details about how to check the kernel version, see How Can I Check the Version of a TaurusDB Instance?

Billing

  • Enabling Dynamic Serverless for an instance with fixed specifications does not change its existing billing factors or mode. Any additional TCUs used beyond the fixed specifications are billed on an hourly basis. For details, see Product Pricing Details.
  • A yearly/monthly instance with Dynamic Serverless enabled will be frozen if it expires and is in arrears.
  • If a yearly/monthly instance with Dynamic Serverless enabled is in arrears, the Dynamic Serverless feature will be disabled.

Constraints

Table 1 Constraints

Phase

Constraints

Before this feature is enabled
  • If the current region supports serverless instances and you want to enable Dynamic Serverless for a pay-per-use or yearly/monthly instance with fixed specifications, submit a service ticket.

    Regions supporting serverless instances: CN North-Beijing4, CN East-Shanghai1, CN South-Guangzhou, AP-Singapore, AP-Bangkok, ME-Riyadh, and CN-Hong Kong

  • This feature is available for the following instance types:
    • Pay-per-use or yearly/monthly x86 instances that have dedicated, fixed specifications and are deployed across AZs
    • Cluster instances (This feature is unavailable for single-node, multi-primary, or serverless instances.)
    • Instances with a CPU-to-memory ratio of 1:4 (Read replica specifications must match those of the primary node.)

After this feature is enabled
  • Read replica addition

    Serverless read replicas cannot be added to fixed-specification instances with Dynamic Serverless enabled. By default, pay-per-use and yearly/monthly read replicas added to such instances will function as dynamic serverless nodes. Their specifications are the same as those of the primary node and cannot be modified. They also use the same serverless compute capacity range.

  • Specification change

    If the specifications of a fixed-specification instance with Dynamic Serverless enabled are changed, Dynamic Serverless is automatically disabled.

  • Mutually exclusive features

    Dynamic Serverless and Auto Scaling are mutually exclusive features. If you have already enabled one for an instance with fixed specifications, you cannot enable the other.

Procedure

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region and project.
  3. On the Instances page, click the instance name to go to the Basic Information page.
  4. In the Configuration area, click Enable Dynamic Serverless under Instance Specifications.
  5. In the displayed dialog box, set Min. TCUs and Max. TCUs and click OK.

    Figure 1 Enabling Dynamic Serverless

    Table 2 Parameters

    Parameter

    Description

    Min. TCUs

    The minimum value for Min. TCUs is defined by the number of vCPUs configured in the current instance specifications. The value of Min. TCUs must be less than or equal to the value of Max. TCUs.

    Max. TCUs

    The minimum value for Max. TCUs is defined by the number of vCPUs configured in the current instance specifications. The maximum value is 32 vCPUs.

  6. Click OK to enable Dynamic Serverless.
  7. Check the result.

    On the Instances page, you can see that the instance status is Configuring dynamic serverless. After 5 to 10 minutes, on the Basic Information page, the instance status changes to Available and the Serverless Information area shows the TCU configurations.

    Figure 2 Serverless information

  8. If you no longer need the Dynamic Serverless feature, click Disable Dynamic Serverless under Instance Specifications in the Configuration area. In the displayed dialog box, click OK.
Parent Topic: Serverless Instances