1 Answer
- Newest
- Most votes
- Most comments
1
The available network bandwidth of an instance depends on the number of vCPUs that it has. The EC2 user guide has links describing the performance of different instance types. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-network-bandwidth.html
You could also consider scaling horizontally, by adding an instance. This would also give you an opportunity to use multiple availability zones and remove a single point of failure.
answered 2 years ago
Relevant content
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
Hi, yes, we have considered all of these, and would like to avoid doubling the current cost with the horizontal scaling since the only bottleneck is the network bandwidth.
Additionally, there seems to be no way to see the network bandwidth credit stats unlikely the CPU or disk credits?
There is no way to change the network bandwidth without increasing the instance size.
You could review the link above to see if there is a similar instance size that offers more bandwidth. For example, a T3 instead of a T2.
We have now split the traffic to two servers now and yet still observing
While we are maximum less than 250Mbps on a .5Gbps baseline on each machine, this doesn't make much sense...
I have a pretty similar question over here with some interesting analysis if you're interested: https://repost.aws/questions/QUv105xDmfQMGUiBbfeYW-iQ/elasticache-shows-network-in-and-out-as-exceeded-but-how