AWS re:Postを使用することにより、以下に同意したことになります AWS re:Post 利用規約

Network traffic limits on EC2 instances

0

I am running a network-intensive task that sends several thousand pings/traceroute packets per second to external IP addresses. I've noticed that the network throughput is high soon after creating the instance, but drops off exponentially after the ping process has been running for more than an hour or so. I've tried this on a variety of instance sizes. Even on a c6.2xlarge (whose stated baseline network bandwidth is 2.5 Gbps), it drops down to around 200 packets a minute. Any ideas why this might be happening? Is there any way I can reserve more bandwidth for my instance?

1回答
1
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.

You can find more information at AWS official documentation .

Specific to c6g instance, you can find the baseline network performance here at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/compute-optimized-instances.html#compute-network-performance

If you would like to get much higher baseline performance, then look for the instance type that ends with letter "n". For example C5n, M5n, C6gn, etc

回答済み 3年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ