Scaling storage and performance

Information about scaling storage, IOPS, and throughput for Db2® SaaS Azure instances.

Each Db2 SaaS Azure instance deploys with 50 GB of disk space and 12,000 IOPS by default. Storage can be scaled up to a maximum of 262,110 GB (approximately 256 TB) in increments of 20 GB starting at 50 GB, while IOPS can be scaled up to a maximum of 320,000 in increments of 100 however will be limited by the IOPS supported by the underlying node type selected. In addition, the instance comes with a default throughput of 500 MB/s, and can be scaled up to a maximum of 4,800 MB/s. Compute can also be scaled by selecting from a list of the VM Types available. When scaling additional VM Nodes and reources attached to the AKS Data Plane will be provisioned in your cloud account.

IOPS scaling is only enabled when disk size is at least 690 GB.

The max throughput that can be scaled to also depends on the IOPS set on the instance. The limit for a particular instance is IOPS * 0.25, and it cannot exceed 4,800 MB/s.

To scale storage from within the console, complete the following steps:

  1. Select Administration from the left side menu.
  2. Select the Compute & storage tab.
    Figure 1. Azure Scale Page
    Azure scale page
  3. Select Edit under the Compute & storage resources.
  4. Select the desired Units for storage, IOPS, and throughput to make changes.
  5. Click Save.
  6. Select Confirm if you are satisfied with the changes.
Figure 2. Azure Scale Confirm
Azure scale confirm

In this documentation, we refer to storage capacity by using the unit GB (Gigabytes) to align with the industry standard terminology. However, the actual provisioning and billing of storage are based on GiB (Gibibytes).

The difference between GB and GiB lies in their numerical representation:

  • GB (Gigabyte) is a decimal unit, where 1 GB equals 1,000,000,000 bytes
  • GiB (Gibibyte), is a binary unit, where 1 GiB equals 1,073,741,824 bytes

A maximum of 3 scale attempts are allowed within a 24 hour period.