简体繁体 English

具有低I / O带宽的t [1 | 2] .micro AWS实例具体意味着什么？

[英]What is specifically meant by t[1|2].micro AWS instances having low I/O bandwidth?

原文 2015-03-16 17:33:13 2 1 amazon-web-services/ amazon-ec2

What is meant by this low I/O bandwidth constraint? 低I / O带宽限制意味着什么？ Does Amazon give a lower priority to I/O operations for t[1|2].micro instances? Amazon是否为t [1 | 2] .micro实例的I / O操作赋予较低的优先级？

What I'm asking specifically is, does Amazon limit the I/O intentionally or is the low I/O a result of the limited resources of the t[1|2].micro instance? 我要特别问的是，Amazon是否故意限制了I / O或低的I / O是t [1 | 2] .micro实例的有限资源的结果？ From what I've read on Amazon, AWS EBS-based magnetic drives have IOPS between 40-200; 根据我在亚马逊上阅读的内容，基于AWS EBS的磁驱动器的IOPS在40-200之间； does the t[1|2].micro instance then provide lower transport capacity per I/O operation? t [1 | 2] .micro实例是否会为每个I / O操作提供较低的传输能力？

This is entirely confusing to me b/ca 7200 RPM drive has IOPS between 75-100 on a desktop computer. 这完全让我感到困惑，b / ca 7200 RPM驱动器在台式计算机上的IOPS在75-100之间。 Why then would IOPS between 40-200 on a t1.micro instance w/an attached EBS-based magnetic disk be considered low? 那么，为什么在附有基于EBS的磁盘的t1.micro实例上，IOPS在40-200之间会被认为低？

Thanks in advance for your help. 在此先感谢您的帮助。

1 个解决方案

EBS volumes are not a single drive. EBS卷不是单个驱动器。 Generally the best way to think of them is more along the lines of a raid volume. 通常，考虑它们的最佳方法更多地是根据突袭量。

So, instances are shared on host hardware. 因此，实例在主机硬件上共享。 Which means that the bandwidth available to the EBS volume is shared among all instances on the host. 这意味着EBS卷可用的带宽在主机上的所有实例之间共享。 Micro instances get the lowest priority of all instances sizes. 微型实例在所有实例大小中的优先级最低。

With a micro instance, even if you have a volume capable of 200 IOPS, depending how noisy your neighbors are, you may not even get close to that. 对于微型实例，即使您的容量为200 IOPS，这取决于邻居的嘈杂程度，您甚至可能无法接近。