You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/mysql/flexible-server/concepts-service-tiers-storage.md
+26-10Lines changed: 26 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Service tiers
3
3
description: This article describes the compute and storage options in Azure Database for MySQL - Flexible Server.
4
4
ms.service: mysql
5
5
ms.subservice: flexible-server
6
-
ms.topic: conceptual
6
+
ms.topic: concept-article
7
7
author: code-sidd
8
8
ms.author: sisawant
9
9
ms.reviewer: maghan
@@ -41,11 +41,11 @@ After you create a server, the compute tier, compute size, and storage size can
41
41
## Service tiers, size, and server types
42
42
43
43
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.
44
-
The detailed specifications of the available server types are as follows:
44
+
45
+
The detailed specifications of the available server types are as follows for **Burstable**:
45
46
46
47
| Compute size | vCores | Physical Memory Size (GiB) | Total Memory Size (GiB) | Max Supported IOPS | Max Connections | Temp Storage (SSD) GiB |
## Memory management in Azure Database for MySQL Flexible Server
111
+
## Memory management in Azure Database for MySQL flexible server
112
+
102
113
In MySQL, memory plays an important role throughout various operations, including query processing and caching. Azure Database for MySQL flexible server optimizes memory allocation for the MySQL server process ([mysqld](https://dev.mysql.com/doc/refman/8.0/en/mysqld.html)), ensuring it receives sufficient memory resources for efficient query processing, caching, client connection management, and thread handling. [Learn more on how MySQL uses memory](https://dev.mysql.com/doc/refman/8.0/en/memory-use.html).
103
114
104
115
### Physical Memory Size (GB)
116
+
105
117
The Physical memory Size (GB) in the table below represents the available random-access memory (RAM) in gigabytes (GB) on your Azure Database for MySQL flexible server.
106
118
107
119
### Total Memory Size (GB)
120
+
108
121
Azure Database for MySQL flexible server provides a Total Memory Size (GB). This represents the total memory available to your server, which is a combination of physical memory and a set amount of temporary storage SSD component. This unified view is designed to streamline resource management, allowing you to focus on the total memory available to your Azure MySQL Server (mysqld) process only.
109
122
Memory Percent (memory_percent) metric represents the percentage of memory occupied by the Azure MySQL server process (mysqld). This metric is calculated from the **Total Memory Size (GB)**. For example, when the Memory Percent metric displays a value of 60, it means that your Azure MySQL Server process is utilizing **60% of the Total memory size (GB)** available on your Azure Database for MySQL flexible server.
110
123
111
124
### MySQL Server (mysqld)
125
+
112
126
The Azure MySQL server process, [mysqld](https://dev.mysql.com/doc/refman/8.0/en/mysqld.html), serves as the core engine for database operations. Upon startup, it initializes total components such as the InnoDB buffer pool and thread cache, utilizing memory based on configuration and workload demands. For example, the InnoDB buffer pool caches frequently accessed data and indexes to improve query execution speed, while the thread cache manages client connection threads. [Learn more](https://dev.mysql.com/doc/refman/8.0/en/mysqld.html).
113
127
114
128
### InnoDB Storage Engine
129
+
115
130
As MySQL's default storage engine, [InnoDB](https://dev.mysql.com/doc/refman/8.0/en/innodb-in-memory-structures.html) uses memory for caching frequently accessed data and managing internal structures like the innodb buffer pool and [log buffer](https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log-buffer.html). [InnoDB buffer pool](https://dev.mysql.com/doc/refman/8.0/en/innodb-buffer-pool.html) holds table data and indexes in memory to minimize disk I/O, enhancing performance. InnoDB Buffer Pool Size parameter is calculated based on the physical memory size (GB) available on server. [Learn more on the sizes of the InnoDB Buffer Pool available](./concepts-server-parameters.md#innodb_buffer_pool_size) in Azure Database for MySQL flexible server.
116
131
117
132
### Threads
133
+
118
134
Client connections are managed through dedicated threads handled by the connection manager. These threads handle authentication, query execution, and result retrieval for client interactions. [Learn more](https://dev.mysql.com/doc/refman/8.0/en/connection-management.html).
119
135
120
136
To get more details about the compute series available, refer to Azure VM documentation for [Burstable (B-series)](../../virtual-machines/sizes-b-series-burstable.md), General Purpose [Dadsv5-series](../../virtual-machines/dasv5-dadsv5-series.md#dadsv5-series)[Ddsv4-series](../../virtual-machines/ddv4-ddsv4-series.md#ddsv4-series), and Business Critical [Edsv4](../../virtual-machines/edv4-edsv4-series.md#edsv4-series)/[Edsv5-series](../../virtual-machines/edv5-edsv5-series.md#edsv5-series)/[Eadsv5-series.](../../virtual-machines/easv5-eadsv5-series.md#eadsv5-series)
@@ -185,16 +201,18 @@ Remember that storage once autoscaled up, can't be scaled down.
185
201
186
202
Azure Database for MySQL flexible server supports pre-provisioned IOPS and autoscale IOPS. [Learn more.](./concepts-storage-iops.md) The minimum IOPS are 360 across all compute sizes and the maximum IOPS is determined by the selected compute size. To learn more about the maximum IOPS per compute size refer to the [table](#service-tiers-size-and-server-types).
187
203
188
-
> [!Important]
204
+
> [!IMPORTANT]
189
205
> **Minimum IOPS are 360 across all compute sizes <br>
190
206
> **Maximum IOPS are determined by the selected compute size. <br>
191
207
192
208
You can monitor your I/O consumption in the Azure portal (with Azure Monitor) using [IO percent](./concepts-monitoring.md) metric. If you need more IOPS than the max IOPS based on compute, then you need to scale your server's compute.
193
209
194
210
## Pre-provisioned IOPS
211
+
195
212
Azure Database for MySQL flexible server offers pre-provisioned IOPS, allowing you to allocate a specific number of IOPS to your Azure Database for MySQL flexible server instance. This setting ensures consistent and predictable performance for your workloads. With pre-provisioned IOPS, you can define a specific IOPS limit for your storage volume, guaranteeing the ability to handle some requests per second. This results in a reliable and assured level of performance. Pre-provisioned IOPS enables you to provision **additional IOPS** above the IOPS limit. Using this feature, you can increase or decrease the number of IOPS provisioned based on your workload requirements at any time.
196
213
197
214
## Autoscale IOPS
215
+
198
216
The cornerstone of Azure Database for MySQL flexible server is its ability to achieve the best performance for tier 1 workloads, which can be improved by enabling server automatically scale performance (IO) of its database servers seamlessly depending on the workload needs. This is an opt-in feature that enables users to scale IOPS on demand without having to pre-provision a certain amount of IO per second. With the Autoscale IOPS featured enable, you can now enjoy worry free IO management in Azure Database for MySQL flexible server because the server scales IOPs up or down automatically depending on workload needs.
199
217
200
218
With Autoscale IOPS, you pay only for the IO the server use and no longer need to provision and pay for resources they aren’t fully using, saving both time and money. In addition, mission-critical Tier-1 applications can achieve consistent performance by making additional IO available to the workload at any time. Autoscale IOPS eliminate the administration required to provide the best performance at the least cost for Azure Database for MySQL flexible server customers.
@@ -205,8 +223,6 @@ With Autoscale IOPS, you pay only for the IO the server use and no longer need t
205
223
206
224
**Cost Savings**: Unlike the Pre-provisioned IOPS where a fixed IOPS limit is specified and paid for regardless of usage, Autoscale IOPS lets you pay only for the number of I/O operations that you consume.
207
225
208
-
209
-
210
226
## Backup
211
227
212
228
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](concepts-backup-restore.md).
@@ -233,7 +249,7 @@ If you would like to optimize server cost, you can consider following tips:
233
249
- Stop the server when not in use.
234
250
- Reduce the backup retention period if a longer retention of backup isn't required.
235
251
236
-
## Next steps
252
+
## Related content
237
253
238
254
- Learn how to [create an Azure Database for MySQL flexible server instance in the portal](quickstart-create-server-portal.md).
239
255
- Learn about [service limitations](concepts-limitations.md).
0 commit comments