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

查看:19
本文介绍了Windows Azure 虚拟机在缩放时访问网络很慢的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在我的小型 azure VM 上运行一些启动脚本 (cmd/bat),其中包括从挂载的 VHD 进行文件传输操作,通常它会在大约 3 分钟内完成(复制文件并使用命令行 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.

可能是什么问题?

我们有检查缓存的想法,但很高兴知道在以下情况下可能存在的任何其他潜在瓶颈.

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: 可能在 blob 上.但同样,我在 40 个文件中有 3GB 的数据,所以每个 blob 60MB/s 应该足以处理它.或者 - 是否可以为所有 blob 设置一个上限?

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?

推荐答案

需要考虑的一件事是 per-storage-account 可扩展性目标.启用地理复制后,您可能会遇到 10Gbps 出口和 20K 事务/秒.以 150 个实例为例,当所有实例都在启动时,您可能会获得 150 x 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 中获取文件,而不是存储在 vhd 中的文件(而 vhd 又存储在页 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屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆