Why does azure take so long

Compute resource provider. Storage resource provider to provision a managed disk according to size and performance layer needed. This also means provisioning replicas to provide redundancy defined.

Then it can provide feedback to the front-end complete! Also, as part of this process, the different providers will also enforce QoS for the different building blocks to ensure consistency for others that also will deploy resources. Within Azure there are multiple components to ensure high availability and scalability.

Now you might argue, now why is Google Cloud a lot faster compared to Azure when provisioning resources? The result however is that a VM is going to be placed on a hypervisor and the VM will only be shown as available and ready once the Azure VM agent is responding back to the fabric controller, but again the storage performance will also impact how quickly the VM will boot.

There are a couple of distinct differences. Many do not take into consideration moving virtual infrastructure to a new platform which might be many miles away which will affect the performance of the VM regarding responding to a request from end-users. In addition, depending on which direction the traffic goes there might be obstacles along the way which might start with your local ISP.

This is also highly dependent on what kind of protocol is used for communication to the VM as well. Depending on what kind of VM size you are using this will also impact two things. For instance, bandwidth for a VM the sum of incoming and outgoing bandwidth, the same applies for bandwidth. If traffic from your internal services is using Azure Firewall for outbound connectivity as well, there might also be that Azure Firewall is scaling which will impact traffic for 10 — 15 minutes each Firewall instance can handle between 1,5 — 3 GBps.

You also must consider which direction the traffic will flow; do you have force tunneling enabled to an on-premises gateway or do you have direct traffic from the public IP of the VM? Network latency will also affect internal communication. Now like West Europe Azure region alone is probably the equivalent of 20 soccer fields.

If you have services that are dependent on low latency connections between a front-end and backend. One new capability that more services in Azure are using now and has been used by Office for some time is routing preferences. This feature ensures that traffic that is a destination somewhere in Azure will be routed to the closest Azure PoP and then routed using the Azure backbone, instead of having traffic routed via ISP to a bunch of other non-optimized traffic flows.

While the network can be a big issue, one of the things that have always troublesome is storage. As mentioned earlier the storage layer in Azure is a separate layer from computing and hence the QoS mechanisms come into play. Secondly, there are other mechanisms that might be it difficult to understand why storage can behave differently sometimes as well.

This cache is also wiped each time the VM is rebooted. In addition, you also have storage tiers now that can provide bursting. Once all of that has synchronized, your app is accessible from the web. The VHD image is probably gigabytes in size, much larger than your app upload. Even on a superfast datacenter network, it takes time to move that much stuff into the VM, unpack it, and boot from it. Also, the load balancer and firewall are probably optimized to make routing requests the highest priority.

Reconfiguring the firewall and load balancer is a lower priority, and has to be done without interrupting traffic flow. Also, note that all this work only has to be done for a new deployment. Updating an existing deployment rolls out much faster - 2 to 3 minutes instead of 20 to 30 minutes. Login Sign Up. Courses Ask a Question. Why does Azure deployment take so long? Reconfiguring the firewall and load balancer is lower priority, and has to be done without interrupting traffic flow.

Also note that all this work only has to be done for a new deployment. Updating an existing deployment rolls out much faster - 2 to 3 minutes instead of 20 to 30 minutes.

He goes into great detail on what's going on inside Azure with some insights into the admittedly slow deployment process.

Original link is no longer working. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Why does Azure deployment take so long? Ask Question. Asked 10 years, 8 months ago. Active 2 years ago. Viewed 46k times. Improve this question. In the meantime we are almost 3 years further and still very slow. Sometimes I think about unboxing a computer then install os then deploy app manually is faster than this.

They're not selling to devs. Show 5 more comments. Active Oldest Votes. Improve this answer.