I have an ASP.net 4.5, talkative, web application that hosts a large (4 core 7 GB) Blue VM has been done. The web application is coupled loosely to the data level through a dedicated WCF service. The application database is hosted by another dedicated (4 core 7 GB) blue VM on a dedicated SQL Server instance. The WCF endpoint communicates with DB VM through an ASP.NET connection string which employs DB VM Public DNS name - e.g. Xyz.cloudapp.net
Both Web and DB VM work in a separate subnet, but both are in the same blue space; Different and later octet value.
When the same solution is running on the same medium (2 core 3.5 GB) blue VM, the issues of latency are very low.
I'm watching the suggestion about reducing DB latency on the web as much as possible.
If you have two VMs, the same data center that needs to be communicated with each other, Do not use your public DNS, create an affinity group, create a virtual network in that affair group, and then both VMs in the virtual network (you may need to close them, delete them without deleting your VHD, and then delete them VNET can create new data from disk). Accessing VM through the DNS (thus via Ezoor LB) connects approximately 0.5 MMS latency for each request - not recommended for any cheaper app.
Comments
Post a Comment