Compute and storage options in Azure Database for MySQL - Flexible Server (Preview)
Azure Database for MySQL - Flexible Server is currently in public preview.
You can create an Azure Database for MySQL Flexible Server in one of three different compute tiers: Burstable, General Purpose, and Memory Optimized. The compute tiers are differentiated by the underlying VM SKU used B-series, D-series, and E-series. The choice of compute tier and size determines the memory and vCores available on the server. The same storage technology is used across all compute tiers. All resources are provisioned at the MySQL server level. A server can have one or many databases.
|Resource / Tier||Burstable||General Purpose||Memory Optimized|
|vCores||1, 2||2, 4, 8, 16, 32, 48, 64||2, 4, 8, 16, 32, 48, 64|
|Memory per vCore||Variable||4 GiB||8 GiB *|
|Storage size||5 GiB to 16 TiB||5 GiB to 16 TiB||5 GiB to 16 TiB|
|Database backup retention period||1 to 35 days||1 to 35 days||1 to 35 days|
* With the exception of E64ds_v4 (Memory Optimized) SKU, which has 504 GB of memory
To choose a compute tier, use the following table as a starting point.
|Compute tier||Target workloads|
|Burstable||Best for workloads that don’t need the full CPU continuously.|
|General Purpose||Most business workloads that require balanced compute and memory with scalable I/O throughput. Examples include servers for hosting web and mobile apps and other enterprise applications.|
|Memory Optimized||High-performance database workloads that require in-memory performance for faster transaction processing and higher concurrency. Examples include servers for processing real-time data and high-performance transactional or analytical apps.|
After you create a server, the compute tier, compute size, and storage size changed. Compute scaling requires a restart and takes between 60-120 seconds, while storage scaling does not require restart. You also can independently adjust the backup retention period up or down. For more information, see the Scale resources section.
Compute tiers, size, and server types
Compute resources can be selected based on the tier and size. This determines the vCores and memory size. vCores represent the logical CPU of the underlying hardware.
The detailed specifications of the available server types are as follows:
|Compute size||vCores||Memory Size (GiB)|
The storage you provision is the amount of storage capacity available to your flexible server. Storage is used for the database files, temporary files, transaction logs, and the MySQL server logs. In all compute tiers, the minimum storage supported is 5 GiB and maximum is 16 TiB. Storage is scaled in 1 GiB increments and can be scaled up after the server is created.
Storage can only be scaled up, not down.
You can monitor your storage consumption in the Azure portal (with Azure Monitor) using the storage limit, storage percentage, and storage used metrics. Refer to the monitoring article to learn about metrics.
Reaching the storage limit
When storage consumed on the server is close to reaching the provisioned limit, the server is put to read-only mode to protect any lost writes on the server. Servers with less than equal to 100 GiB provisioned storage are marked read-only if the free storage is less than 5% of the provisioned storage size. Servers with more than 100 GiB provisioned storage are marked read only when the free storage is less than 5 GiB.
For example, if you have provisioned 110 GiB of storage, and the actual utilization goes over 105 GiB, the server is marked read-only. Alternatively, if you have provisioned 5 GiB of storage, the server is marked read-only when the free storage reaches less than 256 MB.
While the service attempts to make the server read-only, all new write transaction requests are blocked and existing active transactions will continue to execute. When the server is set to read-only, all subsequent write operations and transaction commits fail. Read queries will continue to work uninterrupted.
To get the server out of read-only mode, you should increase the provisioned storage on the server. This can be done using the Azure portal or Azure CLI. Once increased, the server will be ready to accept write transactions again.
We recommend that you set up an alert to notify you when your server storage is approaching the threshold so you can avoid getting into the read-only state. Refer to the monitoring article to learn about metrics available.
We recommend that you set up an alert to notify you when your server storage is approaching the threshold so you can avoid getting into the read-only state. For more information, see the documentation on alert documentation how to set up an alert.
Storage auto-grow is not yet available for Azure Database for MySQL Flexible Server.
The minimum effective IOPS is 100 across all compute sizes and the max effective IOPS is determined by both of the following attributes:
- Compute: the max effective IOPS maybe limited by the maximum available IOPS of the selected compute size.
- Storage: in all compute tiers, the IOPS scale with the provisioned storage size in a 3:1 ratio.
You can scale effective IOPS available by increasing the provisioned storage or moving to a larger compute size (if your IOPS are limited by compute). In preview, the max effective IOPS supported is 20,000 IOPS.
To learn more about the max effective IOPS per compute size, using the combination of both compute and storage, is shown below:
|Compute size||Max effective IOPS|
The maximum effective IOPS is dependent on the maximum available IOPS per compute size. See to the formula below and refer to the column Max uncached disk throughput: IOPS/MBps in the B-series, Ddsv4-series, and Edsv4-series documentation.
Max effective IOPS = MINIMUM("Max uncached disk throughput: IOPS/MBps" of compute size, storage provisioned in GiB * 3)
You can monitor your I/O consumption in the Azure portal (with Azure Monitor) using IO percent metric. If you need more IOPS, you will need to understand if you are restricted by the compute size or the storage provisioned. Scale your server's compute or storage provisioned accordingly.
The service automatically takes backups of your server. You can select a retention period from a range of 1 to 35 days. Learn more about backups in the backup and restore concepts article.
After you create your server, you can independently change the compute tier, compute size (vCores and memory), and the amount of storage, and the backup retention period. The compute size can be scaled up or down. The backup retention period can be scaled up or down from 1 to 35 days. The storage size can only be increased. Scaling of the resources can be done through the portal or Azure CLI.
The storage size can only be increased. You cannot go back to a smaller storage size after the increase.
When you change the compute tier or compute size, the server is restarted for the new server type to take effect. During the moment when the system switches over to the new server, no new connections can be established, and all uncommitted transactions are rolled back. This window varies, but in most cases, is between 60-120 seconds.
Scaling storage and changing the backup retention period are online operations and do not require a server restart.
For the most up-to-date pricing information, see the service pricing page. To see the cost for the configuration you want, the Azure portal shows the monthly cost on the Compute + storage tab based on the options you select. If you don't have an Azure subscription, you can use the Azure pricing calculator to get an estimated price. On the Azure pricing calculator website, select Add items, expand the Databases category, choose Azure Database for MySQL, and Flexible Server as the deployment type to customize the options.
If you would like to optimize server cost, you can consider following tips:
- Scale down your compute tier or compute size (vCores) if compute is underutilized.
- Consider switching to the Burstable compute tier if your workload doesn't need the full compute capacity continuously from the General Purpose and Memory Optimized tiers.
- Stop the server when not in use.
- Reduce the backup retention period if a longer retention of backup is not required.