That way they calculate how much storage traffic they need to handle at any given time. Secondly, if you want to provide a cloud-based model with standardized services, and lastly to ensure the same experience/performance for all customers you need to place QoS in place to ensure consistent performance. First of when Microsoft (and others started building cloud-based platforms) they needed to create a storage layer where it can scale both in performance/capacity regardless of the compute and not dependant on SAN limitations. Now try and convert both the architecture and access to I/O in a cloud-based platform, well it won’t work.
This might affect other VM’s, but we don’t really care since it might not be noticeable. In most environments, you do not have any QoS on storage traffic, so it means that when a VM requires higher bandwidth and or I/O it gets access to it when needed.
If we go even further back with traditional SAN’s there were also high-end connections using FC/iSCSI which connected to the virtualization layer to a backend SAN with either some caching mechanisms or SSD capabilities. With most modern HCI vendors a VM runs with much of the required data running either cached on the local physical host it is running on or stored nearby on an SSD/NVMe drive. The jump from having virtual machines running on a private cloud or existing data center with some form of virtualization (or even modern HCI) where you have high-end storage capacity to a cloud-based platform is going to be a painful jump. NOTE: Much of the content in this blog post is also applicable for the other cloud providers, just replace Azure names with other features or services from the other vendors.ġ: Moving from on-premises to a cloud-based platform However, I wanted to use this blog post to elaborate on why certain things might be a bit slower and other factors that can impact performance secondly features that you can use to enhance performance, and lastly how to troubleshoot if something is not working as intended.
The big picture of things that can get in the way Companies that have been using Azure as a pure IaaS based platform and moved or built new virtual machines on the cloud platform would certainly notice the difference compared to traditional virtual infrastructure. After working with Microsoft Azure for over 10 years now, think this must be the one question that I’ve received the most “ why is my VM running so slow in Azure?”.
0 kommentar(er)
