“高达10 Gbps”的含义EC2 实例中的带宽
我有一个 AWS ec2 c5.large 实例。根据我在这里读到的内容 https://aws.amazon.com/ec2/instance -types/c5/ 它表示网络带宽高达 10 Gbps。
我试图理解这 10 Gbps 就像峰值流量，但我如何知道我可以在这台机器上放置 2 小时的最大持续带宽是多少？
从以下评论中共享的链接 https:// docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-network-bandwidth.html 我得到的信息仍然无法告诉这些较小实例的实际标称流量是多少：
通常，具有 16 个或更少 vCPU（大小 4xlarge 及更小）的实例被记录为具有“最多”指定带宽；例如，“高达 10 Gbps”。这些实例具有基线带宽。为了满足额外的需求，他们可以使用网络 I/O 信用机制来突破其基线带宽。实例可以在有限的时间内使用突发带宽，通常为 5 到 60 分钟，具体取决于实例大小。 实例在启动时接收最大数量的网络 I/O 积分。如果实例耗尽其网络 I/O 积分，它将返回到其基准带宽。只要运行的实例使用的网络带宽少于其基准带宽，它就会获得网络 I/O 积分。停止的实例不会获得网络 I/O 积分。即使实例有可用积分，实例突发也会尽力而为，因为突发带宽是共享资源。
I have an AWS ec2 c5.large instance. According to what I read in here https://aws.amazon.com/ec2/instance-types/c5/ it says that Network Bandwidth is up to 10 Gbps.
I'm trying to understand that those 10 Gbps are like peak traffic but how can I tell what is the maximum sustained bandwidth that I can put on this machine for say 2 hrs?
From a link shared in below comments https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-network-bandwidth.html I got this that still do not tell what is the actual nominal traffic of these smaller instances:
Typically, instances with 16 vCPUs or fewer (size 4xlarge and smaller) are documented as having "up to" a specified bandwidth; for example, "up to 10 Gbps". These instances have a baseline bandwidth. To meet additional demand, they can use a network I/O credit mechanism to burst beyond their baseline bandwidth. Instances can use burst bandwidth for a limited time, typically from 5 to 60 minutes, depending on the instance size.
An instance receives the maximum number of network I/O credits at launch. If the instance exhausts its network I/O credits, it returns to its baseline bandwidth. A running instance earns network I/O credits whenever it uses less network bandwidth than its baseline bandwidth. A stopped instance does not earn network I/O credits. Instance burst is on a best effort basis, even when the instance has credits available, as burst bandwidth is a shared resource.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
根据 2017 年对此来源进行的调查： http://www.deplication.net/2017/08/understanding-ec2-up-to-10-gigabit.html
对于 r4 实例，
因此假设没有任何变化，每“大型”实例大约有 5 分钟的 10Gbps 使用时间。
这与我们观察到的情况一致，即“高达 10Gbps”实际上是突发功能，并且基线带宽性能要小得多。
如果您的应用程序是数据带宽密集型应用，那么 EC2 可能不是正确的选择。
From investigation done at this Source back in 2017: http://www.deplication.net/2017/08/understanding-ec2-up-to-10-gigabit.html
For r4 instances,
So assuming nothing has changed, per 'large' instance you have roughly 5 minutes of 10Gbps usage.
This is consistent with what we have observed, in that the 'up to 10Gbps' is really a burst functionality and the baseline bandwidth performance is much, much smaller.
If your app is data bandwidth intensive, EC2 is probably not the right answer.