Azure平台：scalling实例上下 [英] Azure platform: scalling instances up and down

问题描述

请注意：如果你熟悉Azure的定价模式，就跳转到问题一节

Note: if you are familiar with the Azure pricing model, just jump to the "question" section.

微软将开始收取使用Azure平台的启动 2010年2月1日 。每月的账单将是带宽，存储和其他功能。其中用于计算该法案的因素是的计算时间的。
这后一个因素，但是，有一个误导的名字：它应命名为实例托管时间的代替。引用了Windows Azure的定价页：

Microsoft will begin to charge for the use of the Azure platform starting February 1, 2010. The monthly bill will be a function of bandwidth, storage, and others. Among the factors used to calculate the bill is compute time. This latter factor, however, has a misleading name: it should be named instance hosting time instead. Quoting the windows azure pricing page:

的当开发和测试您的应用程序，开发人员希望删除没有被用来减少计算小时计费的计算实例的

因此​​，让你觉得这是不是的计算小时的，但是的正常运行时间的将收取什么。疑点读取完整的官方回应<一后淡出href=\"http://social.msdn.microsoft.com/Forums/en-US/windowsazure/thread/9ed63b5f-09fa-40fd-8adb-462c4057901f\"相对=nofollow>在MSDN论坛这个问题：

Thus making you think it's not compute hours, but uptime hours what you will be charged for. The doubt fades out completely after reading the official response to this question in MSDN forums:

的我可以证实，每个实例计数（任何角色），你有实例活跃计数所有时间（无论他们多少活动有）。在具有两个Web角色实例和两个工作者角色实例应用程序的情况下，你会被收取四个实例的

0.12 $每个实例/小时，使用N个实例的应用程序将在24 * 30 * 0.12 * N /每月例如=〜$ 86 /月的平均收费。
这个问题恶化的小网站，当你考虑到的事实，你不能少于2情况下，如果你想要的99.9％的服务水平协议申请。

At $0.12/hour per instance, an app using N instances will be billed an average of 24*30*0.12*N/month = ~ $86/month per instance. The matter worsens for small websites when you take into account the fact that you can't have less than 2 instances if you want the 99.9% uptime service level agreement to apply.

所以，小，计算功耗，价格低廉的网站可能不是目标市场的Azure。但对于批处理，负担很可能会消失。

So, a small, compute-power-inexpensive web site is probably not the target market for Azure. But for batch processes, the burden would probably go away.

问

仅在计算功率和计算时间的角度说起的计费，Azure的将是一个批处理一个好的托管选项，只运行了几个小时了一个月，当且仅当您可扩展的（上下！）轻松实例的数量。所以：

Speaking only in terms of compute-power and "compute hours" billing, Azure would be a good hosting option for a batch process that runs only a few hours a month, if and only if you can scale up (and down!) the number of instances easily. So:

• 是否有可能以编程方式放大和缩小在Azure中实例的数量？除了是手动更改配置文件中的任何其他选项？


• 是否有缩小的实例数的任何非显而易见的问题是什么？


• 天青多少时间花费的确认缩放您的应用程序了？

至于后一个问题：采取，你有一个非常大的一些情况（比如1000）45分钟运行的极端情况。如果Azure是不能够的过程结束后，你将被收取另外1000的计算时间小时后服用比例的通知下在15分钟内。

Regarding the latter question: Take an extreme case where you have a very large number of instances (say, 1000) running for 45 minutes. If Azure isn't capable of taking notice of the scaling down within 15 minutes after after the process has ended, you will be charged for another 1000 compute-time hours.

推荐答案

您是否正确，您支付的正常运行时间，不计算时间。

You are correct, you are paying for uptime hours, not compute hours.

有一点需要警惕的是，你支付的部分时间没有任何按比例分配，因此，如果您快速放大和缩小，你是吃满小时。

One thing to be wary of is that you pay for partial hours without any proration, so if you rapidly scale up and down, you are eating full hours.

至于其他人已经提到的，你可以从编程应用程序中放大和缩小。然而，一般来说一个特定的角色将只能访问到它自己的指标（除非你保存指标入库），加上全球资源指标（队列长度等），所以根据CPU利用率等做缩放可能有困难。

As other people have mentioned, you can programatically scale up and down from within your application. however, in general a particular role will only have access to its own metrics (unless you save the metrics into storage), plus any global resource metrics (queue length, etc) so doing scaling based on CPU utilization etc may be difficult.

向上扩展开始几乎立即用一台机器花几分钟旋转起来。没有与目前提供的自旋向上没有的SLA。微软曾表示，实例将拿出在不同的时间，所以，如果你做一个非常大的放大操作，也可能是所有实例都可用之前显著的时间;但某些情况下，将可立即。您无需为实例，直到其完全剥离行动。

Scaling up begins almost instantly with a machine taking a few minutes to spin up. There are no SLAs with spin-up offered currently. Microsoft has said that instances will come up at different times, so if you do a very large scale-up operation, it may be significant time before all instances are available; but some instances will be available almost immediately. You are not charged for an instance until it is fully spun-up.

缩小偏偏几乎立即，但你无法控制哪些实例被用于比例缩小，因此，如果您的实例的50％处于闲置状态，你做了50％的比例缩小，你可以杀死所有的有效的实例，并且该工作需要的previously空闲实例重新启动。你必须确保你的设计支持工作的好重启（如果你使用的队列超时，这可能主要是自动发生）

Scaling down happens almost immediately, but you cannot control which instances are used for the scale-down, so if 50% of your instances are idle and you do a 50% scale-down, you may kill off all of your active instances, and that work would need to be restarted on the previously idle instances. You must make sure your design supports good restarting of work (if you use queue timeouts, this can happen mostly automatically)

有开始出现，旨在帮助在缩放一些第三方解决方案。一，我看着那个看起来很有希望是AzureWatch从 http://paraleap.com/ 它提供如自动一些事情根据利用率，queuelength，日程安排等Web和辅助角色的上/下缩放。

There are a few 3rd party solutions starting to appear that aim to help out in scaling. One that I have looked at that looks promising is AzureWatch from http://paraleap.com/ which offers some things like automatic up/down scaling of web and worker roles based on utilization, queuelength, schedule etc.

这篇关于Azure平台：scalling实例上下的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！