Blog Post

Azure Database for MySQL Blog
2 MIN READ

Announcing Autoscale IOPS (Public Preview) for Azure Database for MySQL - Flexible Server

Bashar-MSFT's avatar
Bashar-MSFT
Icon for Microsoft rankMicrosoft
Oct 13, 2022

How many pre-provisioned IOPS does your workload need to run smoothly and efficiently? This seems like an easy question to ask but difficult to answer, given that if you over-provision the IOPS you’ll incur extra charges and if you under-provision it, it’ll cause some serious throttling and performance degradation. And the situation only gets trickier if your workload is unpredictable or bursty. While scaling IOPS after-the-fact doesn’t cause a server restart, scaling it manually becomes a tedious and tough task in the long run.

 

With Azure Database for MySQL – Flexible Server, we’re on a mission to enable customers to bring their MySQL workloads with a minimal operational burden associated with database management, all the while maintaining maximum control. Today, we are introducing Autoscale IOPS to let you enjoy worry free IO management in Azure Database for MySQL Flexible Server. The server scales IOPs up or down automatically depending on your workload needs!

 

With Autoscale IOPS, we’re making it easier and more cost-effective for customers to run their mission-critical workloads on Azure Database for MySQL – Flexible Server. The best part is that you pay only for the IO you use and no longer need to provision and pay for resources which aren’t fully used, saving both money and time. In addition, mission-critical Tier-1 applications can achieve consistent performance by making additional IO available to the workload at any time. Autoscale IO eliminates the administration required to provide the best performance at the least cost for Azure Database for MySQL customers.

 

Demo Video

 

 

 

How can I switch from pre-provisioned IOPS to Autoscale IOPS?

 

Simple navigate on the Azure Portal to your Azure Database for MySQL flexible server. In the “Compute+Storage” blade, choose “Auto scale IOPS” option.

 

 

Please note that Autoscale IOPS is billed on usage in per million request increments. Learn more about pricing details.

 

Summary:

 

Autoscale IOPS is one new feature we are adding to Azure Database for MySQL – Flexible Server as part of our continuous work to provide customers with a MySQL server tuned readily with an optimal and cost-effective out-of-the-box performance. Try this feature out and let us know your feedback by reaching out to us at AskAzureDBforMySQL@service.microsoft.com. Thank you!

 

Updated Oct 13, 2022
Version 2.0
Azure Database for MySQL
Azure Database for MySQL - Flexible Server
Microsoft Ignite 2022
MySQL
performance
  • VVainio's avatar
    VVainio
    Copper Contributor
    Dec 30, 2022

    Hello,

     

    I would be curious to ask, do you consider that there would be any scenario where the pre-provisioned IOPS would be preferable over using the auto scale feature? In other words, are there some known limitations or drawbacks for using the auto scale feature?

     

    BR, Vesa

  • Bashar-MSFT's avatar
    Bashar-MSFT
    Icon for Microsoft rankMicrosoft
    Oct 19, 2022

    That is correct but we can do it for your server manually, support engineer should be able to reach out to engineering and we can do it manually for your server.

  • hidiho's avatar
    hidiho
    Copper Contributor
    Oct 18, 2022

    Thanks for your reply Bashar-MSFT, I already contacted Azure Support. Reply is:
    "Auto scale IOPS preview feature only supports servers built after 10/09/2022 by now. Hotfix will start deploying this week, should be finished globally in 1~2 weeks. All of these problems will then be resolved."

     

    So hopefully it should work in two weeks, right? :smile:

  • hidiho's avatar
    hidiho
    Copper Contributor
    Oct 14, 2022

    This is a great announcement!

    Unfortunately, I'm not able to activate it, I just get following error:

    {
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "InternalServerError",
      "message": "An unexpected error occured while processing the request. Tracking ID: '13f34f31-44ce-415e-8109-7d60b37ef463'"
    }
  ]
}

     I'm in region "Germany West Central", could that be the cause?