Comments on: Network Latency Inside And Across Amazon EC2 Availability Zones http://orensol.com/2009/05/24/network-latency-inside-and-across-amazon-ec2-availability-zones/ Oren Solomianik's Blog Fri, 12 Mar 2010 18:00:46 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: bryanl http://orensol.com/2009/05/24/network-latency-inside-and-across-amazon-ec2-availability-zones/comment-page-1/#comment-1220 bryanl Tue, 26 May 2009 13:09:36 +0000 http://orensol.com/?p=226#comment-1220 Also, ICMP isn't a good determination of latency due to the possibility of being classified as a low prioritization by the connection routers. I think a better test would be to fire up more instances in different zones and push traffic between them and counting the bandwidth that way. Also, ICMP isn’t a good determination of latency due to the possibility of being classified as a low prioritization by the connection routers. I think a better test would be to fire up more instances in different zones and push traffic between them and counting the bandwidth that way.

]]> By: Overview of Amazon EC2 Network Latency | Cirrus Nine http://orensol.com/2009/05/24/network-latency-inside-and-across-amazon-ec2-availability-zones/comment-page-1/#comment-1219 Overview of Amazon EC2 Network Latency | Cirrus Nine Tue, 26 May 2009 12:52:21 +0000 http://orensol.com/?p=226#comment-1219 [...] Good Data [...] [...] Good Data [...]

]]> By: Eric Hammond http://orensol.com/2009/05/24/network-latency-inside-and-across-amazon-ec2-availability-zones/comment-page-1/#comment-1210 Eric Hammond Sun, 24 May 2009 20:10:09 +0000 http://orensol.com/?p=226#comment-1210 A single availability zone is like a big data center. The latency between two arbitrary instances within an availability zone could vary depending on how close they are to each other within that data center in the network topology. Another good test would be to fire up 20 instances inside a single availability zone and measure the variability of latency between them. Also, the names of availability zones are assigned randomly within each account. Your account's "us-east-1a" may be my account's "us-east-1c". A single availability zone is like a big data center. The latency between two arbitrary instances within an availability zone could vary depending on how close they are to each other within that data center in the network topology. Another good test would be to fire up 20 instances inside a single availability zone and measure the variability of latency between them.

Also, the names of availability zones are assigned randomly within each account. Your account’s “us-east-1a” may be my account’s “us-east-1c”.

]]>