Azure 计算实例

发布于 2024-12-27 20:38:10 字数 217 浏览 3 评论 0原文

在 Azure 上,我可以以 1 个小型实例的价格获得 3 个额外的小型实例。我不担心我的网站无法扩展。

还有其他原因让我不应该选择 3 个特小号而不是 1 个小号吗?

请参阅:Azure 定价计算器

On Azure I can get 3 extra small instances for the price 1 small.I'm not worried about my site not scaling.

Are there any other reasons I should not go for 3 extra small instead of 1 small?

See: Azure pricing calculator.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

与君绝 2025-01-03 20:38:10

超小型实例仅限于大约。 NIC 上的带宽为 5Mbps(小型、中型、大型和 XL 的每个核心约为 100Mbps),并且 RAM 小于 1GB。因此,假设您正在运行存储非常密集的东西。您可能会遇到访问 SQL Azure 或 Windows Azure 存储的瓶颈。

使用 RAM:如果您正在运行 MongoDB 等第 3 方应用程序,则可能会遇到内存问题。

从可扩展性的角度来看,您可以将负载分散到 2 或 3 个 Extra Small 实例上,并且您将获得良好的 SLA,这是正确的。只需确保您的内存和带宽足以满足您的性能目标。

有关每个实例大小的确切规格(包括 NIC 带宽)的更多详细信息,请参阅此MSDN 文章

An Extra Small instance is limited to approx. 5Mbps bandwidth on the NIC (vs. approx. 100Mbps per core with Small, Medium, Large, and XL), and has less than 1GB of RAM. So, let's say you're running something that's very storage-intensive. You could run into bottlenecks accessing SQL Azure or Windows Azure storage.

With RAM: If you're running 3rd-party apps, such as MongoDB, you'll likely run into memory issues.

From a scalability standpoint, you're right that you can spread the load across 2 or 3 Extra Small instances, and you'll have a good SLA. Just need to make sure your memory and bandwidth are good enough for your performance targets.

For more details on exact specs for each instance size, including NIC bandwidth, see this MSDN article.

情徒 2025-01-03 20:38:10

查看细则 - 与超小型实例相比,小型实例的 I/O 性能应该要好得多。我不确定这是否是由于技术相关瓶颈或业务决策造成的,但事实就是如此。

另外,我猜测操作系统在每个实例中都会占用一些 RAM,因此在 3 个小型实例中,它会占用 3 次,而不是在小型实例中只占用一次。这将减少实际可用于您的应用程序需求的资源。

Look at the fine print - the I/O performance is supposed to be much better with the small instance compared to the x-small instance. I am not sure if this is due to a technology related bottleneck or a business decision, but that's the way it is.

Also I'm guessing the OS takes a bit of RAM in each of the instances, so in 3 X-small instances it takes it up three times instead of just once in a small instance. That would reduce the resources that are actually available for your application needs.

ま柒月 2025-01-03 20:38:10

虽然从理论上讲,3 个超小型实例可能等于甚至比 1 个小型实例更好,但请记住,超小型实例没有专用核心,并且其原始计算资源与其他租户共享。我尝试过这些超小型实例,试图为小负载网站省钱,但必须说,只是出现了一些中断或性能糟糕的情况,我发现这是不可接受的。

简而言之:我不会在任何类型的生产环境中使用超小型实例

While 3 xtra-small instances theoretically may equal or even be better "on paper" than one small instance, do remember that xtra-small instances do not have dedicated cores and their raw computing resources are shared with other tenants. I've tried these xtra-small instances in an attempt to save money for tiny-load website and must say that there were simply outages or times of horrible performance that I've found unacceptable.

In short: I would not use xtra-small instances for any sort of production environment

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文