3 ms·
Well, at the moment i can't pin it down to EC2, but it's the only thing i can imagine it'd be. The network/cpu/memory usage is all healthy, and there's nothing
by chubs 15y ago
Well, at the moment i can't pin it down to EC2, but it's the only thing i can imagine it'd be. The network/cpu/memory usage is all healthy, and there's nothing in the kernel log, so that's what i'm guessing is the cause. Although i may be wrong.
- csarva 15y agoWe've observed the bottleneck to be an upper limit on packets/sec for a given instance type. On an m1.large this is about 100k/sec. I believe it's due to the virtual NIC just not being fast enough to handle high traffic loads. The rightscale folks found the same thing: http://blog.rightscale.com/2010/04/01/benchmarking-load-balancers-in-the-cloud/ http://blog.rightscale.com/2010/04/01/benchmarking-load-bala...