Geek asks and answers

Delay between two Azure VMs

I have ASP.NET 4.5, chatty, a web application that is hosted on one large (4 cores 7GB) Azure VM. The WEB application is loosely connected to the data layer through a special WCF service. The application database is hosted by a special instance of SQL Server on another large (4 core 7GB) Azure VM. The WCF endpoint communicates with the DB virtual machine through an ASP.NET connection string that uses the public DNS name of the database database — for example, xyz.cloudapp.net.

Both the WEB and DB virtual machines are on a different subnet, but both are in the same Azure location; differing in the second and subsequent octet values.

When running the same solution on the same medium (2 cores 3.5 GB), Azure VM problems with the delay are much lower.

I am looking for suggestions on how to minimize the delay between WEB and DB.

+3
source share
2 answers

If you have two virtual machines in the same data center that must communicate with each other, do not use their public DNS. Create an Affinity group, create a virtual network in this affinity group, and then place both virtual machines on the virtual network (you may need to close them, delete them without deleting their VHD, and then create them from data disks in the new VNET). Access to virtual machines via DNS (thus, through Azure LB) adds about 0.5 ms latency to each request - it is not recommended for a chat application.

+2
source

, , . ? - DNS ( ). , , , , Azure Fabric ( URL ).

+3

More articles:


All Articles