networking - 区域虚拟网络内的关联组是否仍然具有性能优势？

Question

现在有新的 Azure Regional Virtual Networks feature跨越一个区域，使用关联组是否有性能优势？在链接的博客文章的常见问题解答部分中，写着

Do I incur any performance degradation for services running inside a Regional Virtual Network?

Virtual network is only a logical boundary, it does not dictate where the deployments in the VNet actually go to. If for some reason, you need services to be in the same Affinity group, you can still do that inside a regional virtual network. During deployment you will have to specify the Affinity group to which the hosted service should be bound to. The only restriction would be, that the Affinity groups should belong to the same region as the Regional Virtual network.

If you do not bind your hosted service to an Affinity group, and deploy services directly to the Regional Virtual Network, your deployments will be placed in a scale unit inside the region the Virtual Network is bound to.

我感觉建议不再使用亲和性组(基于这篇文章和其他一些帖子，也许这是我的 Azure 和/或英语理解能力)，但是服务和数据是否会位于同一位置那么在数据中心呢？

<编辑:当然，在写完这篇文章后，我发现了一篇 MSDN 文章 About Regional VNets and Affinity Groups for Virtual Network其中指出

Previously, when creating a virtual network (VNet) you were required to associate the VNet with an affinity group, which was in turn, associated with a Region. This requirement has changed. Now VNets are associated directly with a Region (Location) in the Management Portal. This allows you more freedom when creating your VNets. You can still associate your cloud services with affinity groups when appropriate, but you are not required to do so.

The Region represents where the Virtual Network overlay will be. Anything you deploy to the virtual network will be physically located in the Region. If you want to further designate that you want your resources in close proximity physically to each other within the same region, you can specify an affinity group for those particular resources. That would mean that not only are those resources in the same physical location, they are very close to each other in the datacenter.

因此，我认为使用关联组会带来性能优势。

<编辑:我能找到的关于亲和性组的小性能优势和用例的最明确来源可以在 Convective blog post Affinity Groups in Azure 找到。 .

An affinity group serves two purposes:

1. colocation of cloud service and storage account
2. host for an affinity group VNET

The second of these is now deprecated. The first is still possible but has not been emphasized as the latency optimization it was prior to the upgrade of the Azure network in 2012. In fact the standard way to deploy a VM in the Azure Portal does not support the simultaneous creation of a cloud service in an affinity group and a regional VNET. This confuses people who try to satisfy the modern best practice of using a regional VNET for deployments and the historic best practice of creating a cloud service in an affinity group.

At this point there seems to be little reason to deploy a cloud service into an affinity group. However, as with other deployment choices it might be wise for people to test this out for their specific workloads.

Answer 1

从未明确证明使用亲和组会带来性能/延迟方面的好处。关于这些好处(或缺乏这些好处)的报道差异很大，而且大部分都是轶事。