I/O performance bursting for high-performance cloud disks

更新时间:
复制 MD 格式

If your workload fluctuates or experiences frequent traffic peaks, you can enable the I/O performance bursting feature for your high-performance cloud disk. This feature allows your cloud disk's IOPS to exceed the standard maximum, providing higher I/O capacity to handle sudden business demands during peak times.

Overview

After you enable I/O performance bursting for a high-performance cloud disk, the maximum IOPS and throughput limits for the instance increase. The following table compares the performance with and without this feature enabled.

Note

When you enable I/O performance bursting on the primary node, the feature is also automatically enabled on the secondary node. However, it is not automatically enabled on read-only instances. You must enable it separately on the details page of each read-only instance.

Scenario

Maximum IOPS

Maximum throughput

I/O performance bursting disabled

min{Maximum IOPS for the instance type, 1800 + 50 × Storage capacity, 50000}

min{Maximum I/O bandwidth for the instance type, 120 + 0.5 × Storage capacity, 350}

I/O performance bursting enabled

min{Maximum IOPS for the instance type, 1000000}

min{Maximum I/O bandwidth for the instance type, 4000}

Note
  • When throughput reaches its limit, it can affect IOPS. Similarly, when IOPS reaches its limit, it can affect throughput.

  • The formula above does not apply to cloud disk instances of general-purpose instance types because they share resources and cannot guarantee maximum IOPS and maximum I/O bandwidth.

  • You can calculate the IOPS that corresponds to the maximum I/O bandwidth of the instance type as follows: Maximum I/O bandwidth of the instance type (Gbit/s) * 1024 * 1024 / 8 / 8. In this formula, the first 8 indicates that 1 byte = 8 bits, and the second 8 indicates that ApsaraDB RDS for SQL Server uses a data block size of 8 KB for a single read/write operation.

Use cases

High-performance cloud disks are suitable for scenarios with high or fluctuating I/O workloads.

Workload peaks, large transactions, full table scans, and queries that return large amounts of data can cause the I/O load to increase. In some cases, your CPU, memory, and storage space may be sufficient, but I/O utilization is approaching or has reached 100%. In this situation, you would typically need to upgrade the instance configuration or storage level (for example, from PL1 to PL2).

  • If you do not upgrade, an I/O load that exceeds the instance's I/O limit can cause performance degradation, query timeouts, and even connection exceptions.

  • If you upgrade the instance configuration to meet I/O performance needs, this may result in idle and wasted CPU, memory, and storage resources.

  • If you upgrade the storage level, you can fully utilize I/O performance in the short term, but this wastes resources and money when the I/O load decreases.

The I/O performance bursting feature of high-performance cloud disks solves these problems. When this feature is enabled, I/O performance bursting is automatically triggered during high I/O loads to increase the I/O limit. When the I/O load drops, the limit automatically returns to the baseline. This provides a Serverless I/O performance model that helps you avoid wasting I/O resources and costs.

Benefits

The I/O performance bursting feature is more cost-effective than upgrading the instance configuration or storage level.

  • You are billed only for the burst I/O usage.

  • Burst I/O usage is calculated by the second.

  • The feature includes a free quota for I/O performance bursting. You are charged only for usage that exceeds this free quota.

Prerequisites

Your ApsaraDB RDS for SQL Server instance must meet the following requirements:

  • Storage type: high-performance cloud disk

  • Instance billing method: subscription or pay-as-you-go (not supported for Serverless instances)

Note

To change the storage type of an instance, see Change ESSD to a high-performance cloud disk.

Impacts

Enabling or disabling the I/O performance bursting feature does not cause a transient disconnection and typically does not affect your services. However, in rare cases, instance IOPS may fluctuate. Therefore, we recommend that you perform this operation during off-peak hours.

Usage notes

Enabling or disabling I/O performance bursting takes several minutes. The exact duration depends on the instance's usage, such as read and write traffic.

Billing

The I/O performance bursting feature for high-performance cloud disks is subject to a promotional fee waiver. Starting from April 16, 2024, the feature is free to use. When the promotion ends, billing will commence. You will still receive a free quota, and you are charged only for usage that exceeds it. The billing standards are as follows:

Unit price of I/O performance bursting

Hourly I/O performance bursting fee for an instance = (Total I/O performance burst volume of all nodes - free quota) × Unit price

Unit price of I/O performance bursting: CNY 0.02 per 10,000 I/Os.

Note

The fees for I/O performance bursting on high-performance cloud disks for ApsaraDB RDS instances (including primary and secondary nodes) are billed on a pay-as-you-go basis. Bills are generated hourly. Usage is billed in units of 10,000 I/Os. Usage of less than 10,000 I/Os is rounded up to 10,000 I/Os for billing.

Free quota for I/O performance bursting

The free quotas for I/O performance bursting on high-performance cloud disks vary based on the ApsaraDB RDS instance specifications.

Instance Edition

Free quota

Basic Edition instances

300,000 I/Os per hour

High-availability Edition instances

600,000 I/Os per hour

Cluster Edition instances

800,000 I/Os per hour

Instance I/O performance bursting amount: The sum of the burst amounts from all nodes in the instance.

Instance Edition

Instance burst amount

Basic Edition

I/O performance bursting amount of the single node

High-availability Edition

Burst amount of the primary node + Burst amount of the secondary node

Cluster Edition

Burst amount of the primary node + Burst amount of all secondary nodes

Note
  • When the primary node is under high I/O pressure and generates burst I/O, the secondary node also generates a corresponding amount of burst I/O to ensure data and service consistency. The I/O performance bursting amount of the secondary node is nearly identical to that of the primary node.

  • You must enable the I/O performance bursting feature for read-only instances separately. The billing standards are the same as for the primary instance. If a read-only instance is a High-availability Edition instance, the fee includes the I/O performance bursting costs for both its primary and secondary nodes.

Single-node I/O performance bursting amount: (Usage exceeding baseline IOPS or throughput) × Duration

Note

Baseline I/O performance is the maximum IOPS and throughput of a high-performance cloud disk when I/O performance bursting is disabled.

Example scenario

A user purchases a High-availability Edition instance with a 200 GB high-performance cloud disk (one primary and one secondary node). The baseline IOPS for this instance is 12,000.

You enable I/O performance bursting. During the hour from 00:00:00 to 01:00:00, performance bursts occur from 00:00:00 to 00:00:27 and from 00:53:00 to 00:53:33. During these periods, IOPS remained at 22,000. For the rest of the hour, the IOPS does not exceed the baseline value, and no bursting occurs.

Burst duration

Total burst duration: 27s + 33s = 60 seconds.

Single-node burst I/O amount for the hour

(22,000 - 12,000) × 60 = 600,000 I/Os

Total instance burst I/O amount for the hour

600,000 (primary) + 600,000 (secondary) = 1,200,000 I/Os

Billing example

Assume that the I/O performance bursting amount for a High-availability Edition instance is 602,000 I/Os in one hour. The fee is calculated as follows:

Actual burst I/O amount

602,000 I/Os per hour

Free quota

600,000 I/Os per hour

Overage

2,000 I/Os

Actual burst I/O charge

10,000 I/Os × CNY 0.02 per 10,000 I/Os = CNY 0.02

Enable or disable I/O performance bursting

  1. Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the instance ID.

  2. In the Basic Information section, you can find the switch to enable or disable I/O performance bursting.

    Click High-performance Cloud Disk Switch Settings to the right of High-performance Cloud Disk. In the dialog box that appears, turn the I/O performance bursting switch on or off.

Related documents

  • For information about other storage types supported by ApsaraDB RDS for SQL Server, see Storage types.

  • If you face high storage pressure and want to reduce storage costs, use the database-level Archive Data to OSS feature for ApsaraDB RDS for SQL Server.