3

为什么各种上传方式的包上传速度差别这么大。

我用来部署的方法是

  1. 在 VS2013 中：上传速度很慢
  2. Powershell Commandlets：再次非常慢
  3. Azure 门户：速度极快

如果速度相差几秒钟或一两分钟，我不会抱怨，但我说的是 45MB 部署包的 10 分钟。

方法 1 和 2 在新西兰使用高速宽带需要超过 45 分钟。通过方法 3 上传仅需 30 秒。

有些事情不太对劲。

我们的网络没有问题，我也可以从其他网络模拟这个。

4

3 回答 3

1

我可以确认从 Visual Studio 部署的问题比直接上传包的时间要长得多，据我所知，这是自 Azure 的第一个版本以来已知且常见的问题。

尽管如此，我想指出的是，通过 Azure 门户上传只是一种数据传输，在部署包后，服务需要更多时间才能响应，而在 VS 部署之后，服务会在部署完成后立即响应. 由此我得出结论，部署时间的差异可能是由于为您的云服务配置了云架构（创建、运行或重新配置主机操作系统 VM）。

于 2013-05-24T07:30:42.187 回答
0

I think I've seen why Visual Studio takes so long to do the upload. If you start up Fiddler while the update is happening you'll see that Visual Studio is uploading the package in 65k blocks in sequence. As you're in NZ you get our wonderful high latency to US servers, so sending lots of smallish requests is not optimal.

If you use a dedicated storage explorer they're usually much more clever and if the file you're uploading is large it will use larger blocks and also upload them in parallel.

于 2015-02-23T23:55:33.160 回答
0

From what I've seen of Azure publishing using Visual Studio vs the Azure Portal, there seems to be no significant difference except for the time it takes to upload the package. As the original poster stated, the Portal is extremely fast; whereas, Visual Studio takes forever to upload the package. I didn't realize the difference for a long time until I tried using the Portal one day just to see how that process worked and I was floored by the difference in speed.

I'd definitely recommend using the Portal vs Visual Studio. One caveat, you seem to need to use Visual Studio the first time around to create the Azure Tools certificate. Not sure if there's a way to create it without Visual Studio.

于 2013-11-07T21:08:18.393 回答