缩放时的Windows Azure虚拟机很慢接入网络 [英] Windows Azure virtual machine is slow to access network when scaling

问题描述

我跑我的天蓝色小一些虚拟机启动脚本（CMD / BAT），其中包括从安装一个VHD文件传输操作，通常它大约3分钟（复制文件并提取与500MB的〜zip文件完成命令行7Z）。

I'm running some startup scripts (cmd/bat) on my small azure VM which include a file-transfer operation from a mounted VHD, and normally it finishes in about 3 minutes (copying files and extracting ~500Mb zip file with command-line 7z).

当我向外扩展至〜150的情况下，相同的操作是很慢的（总共最多15分钟，其中大部分是由7Z使用）。而且，这是最慢的，完成启动过程中的节点是很难获得在第一使用MSTSC（动画滞后，需要花费大量的时间来登录），但可能不相关

When I scale out to ~150 instances, the same operation is very slow (up to 15 minutes in total, most of which is used by 7z). Also, the nodes which are the slowest to complete the bootup procedure are very hard to access at first using mstsc(animation is lagging and takes a lot of time to log in), but that might not be related.

这可能是什么问题呢？

What could be the problem?

我们有想法检查缓存，但它会很高兴知道这可能是在以下情况present任何其他潜在的瓶颈。

We had the idea to examine the cache, but it would be nice to know of any other potential bottleneck which may be present in the following situation.

更新：
我试着提取在D：\\驱动器，而不是在C提取它：\\并同时扩展到200，解压缩需要大约一分钟！因此，它似乎是一个问题是，C：\\上可能有斑点。但同样，我有数据，40个文件的3GB，让每一滴60MB /秒应该足够处理它。或者 - ？它可以是我们为所有斑点上限的情况下

UPDATE: I tried extracting on the D:\ drive instead of extracting it on the C:\ and while scaling to 200, the unzip takes about a minute! So it seems like the problem is that C:\ might be on the blob. But again, I have 3GB of data in 40 files, so 60MB/s per blob should be enough to handle it. Or - can it be the case that we have a cap for the all blobs?

推荐答案

有一点要考虑的是每个存储帐户<一个href=\"http://blogs.msdn.com/b/windowsazure/archive/2012/11/02/windows-azure-s-flat-network-storage-and-2012-scalability-targets.aspx\"相对=nofollow>存储帐户的可扩展性目标。启用georeplication，你有10Gbps的出口和20K交易/秒，你可能会碰到。图150的情况下，你可能会拉动150×100Mbps的或15Gbps的为所有实例都启动。

one thing to consider is the per-storage-account scalability target of a storage account. With georeplication enabled, you have 10Gbps egress and 20K transactions/sec, which you could be bumping into. Figure with 150 instances, you could potentially be pulling 150 x 100Mbps, or 15Gbps as all of your instances are starting up.

不知道你的问题的挂载VHD的一部分。随着Azure中的驱动器安装，只有一个虚拟机实例可以在任何给定的时间安装到驱动器。对于这种类型的文件复制操作的，通常你直接从一个存储的blob抢文件，而不是存储在虚拟硬盘（其中，反过来，被存储在一个页的blob）的文件。

Not sure about the "mounted VHD" part of your question. With Azure's drive-mounting, only one virtual machine instance can mount to a drive at any given time. For this type of file-copy operation, typically you'd grab a file directly from a storage blob, rather than a file stored in a vhd (which, in turn, is stored in a page blob).

修改：只是想提一提，一个单独的BLOB限制为60MB /秒（在博客文章中，我引用的也提到）。这也可以与您的节流。

EDIT: Just wanted to mention that an individual blob is limited to 60MB/sec (also mentioned in the blog post I referenced). This could also be related to your throttling.

这篇关于缩放时的Windows Azure虚拟机很慢接入网络的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！