It caught my eye the other day that Microsoft announced an equivalent to Amazon Web Services’ Direct Connect offering, i.e. the ability to connect from your premises to your cloud deployment without going over the Internet. The press release says this capability is “expected to be available in first half of 2014” – and I assume that this initial launch will be US only with Europe to follow later, although it doesn’t say.

Smart421 was a Direct Connect launch partner in the European region for AWS back in Jan 2012, although the initial US launch was way back in August 2011. So going on that basis, I can now put a crude estimate on how far behind AWS the Azure platform really is – at least two and a half years :)

Anyway, now is as good a time as any to share some brief stats from our real world experience of deploying Direct Connect for the European region. I’m not aware of much data in the public domain about Direct Connect latency measurements in the European region – so if you know of some, please comment on this post to let me know.

On a 1 gigabit connection, for an ICMP (i.e. ping) round trip we typically see a latency of circa 12-13ms for Direct Connect versus 33ms via a VPN over the Internet, i.e. about a 60% reduction in latency.


This data needs to be considered carefully as there are a multitude of factors at play here depending on the specific customer environment and requirements – such as the Internet connectivity for the VPN, and crucially where the customer “on-premises” equipment is in network terms with respect to the AWS Direct Connect location in London Docklands. Also any comparison will vary depending on time of day etc. I’m deliberately not providing any stats on achieved bandwidth here as there are just too many factors involved – principally that the limiting factor is likely to be any MPLS connectivity involved in the architecture rather than Direct Connect itself.

Still – it’s interesting data nonetheless…thanks to ‘Smartie’ Wayne for compiling the data.

Please share this blog using the social buttons below or short URL

Please take a moment to Rate and Like this Post. Our readers want to see YOUR opinion so please post a Comment.

AlarmClockContinuing our fascinating series (sic) of Amazon Web Services related latency measurements…we’ve already looked at the round trip time between the UK and the US vs the EU region, so now our attention has turned to the latency between availability zones (AZs) in the EU region.

The network latency between AZs is critical to designing and implementing fault tolerant applications on AWS, as the design assumption is that synchronous transactional data replication is always feasible, and you can seamless fail over from one Relational Database Node (RDS) node to another “standby” replica in another AZ etc. So we thought we’d measure it!

One of my colleagues collected some measurements between 4 x Linux t1.micro instances (2 running apache & 2 running http-ping scripts) between EU zones. The scripts were scheduled to run every 5 mins (via cron) with each executing 20 x http-ping requests and returning the average response time in milliseconds. We also measured the latency of the http-ping requests via both the private and public addresses of the corresponding web server.

As a control measure, we also measured the average latency for “localhost” to respond, to allow us to eliminate the web server response time from the measurements. This worked out to be as follows:

  • Roundtrip to localhost – round-trip min/avg/max = 0.9/1.0/1.3 ms
  • Roundtrip to a public IP in the same AZ – round-trip min/avg/max = 1.3/1.4/2.7 ms

And here are the results of measurements across the AZs – first for the private IP addresses (click the image to view in full size):


…and for the public IP addresses:


So in summary, the roundtrip between AZs using public IP addresses works out to be about 4ms minimum, and once you take off the minimum 1.3ms experienced between public IPs in the same AZ, and dividing by 2 (as it’s a roundtrip), then the latency between AZs in the EU region works out to be about 1.35ms minimum. Pretty quick really…

Imagine that you want to deploy some components entirely within one Amazon Web Services (AWS) region – which region should you choose? Well, US-East is cheaper than EU-West (e.g. by 11.8% for the smaller on-demand instances), so that’s quite attractive – if your deployment is not tied for legal reasons to a European deployment. Obviously for most UK-centric organisations, the US is further away (!) and so network latencies should be greater…but are they? It seems obvious but before we ruled out a potential 10%+ saving for our customers, we thought we’d do some measurements.

And the answer is…

us-east-1d, average round trip time = 231ms

eu-west-1a, average round trip time = 96ms

This was based upon using http-ping to check the average round trip time of HTTP requests from our Ipswich development centre in the UK. So phew, the laws of physics still hold true even in a cloud world :)


Get every new post delivered to your Inbox.

Join 1,084 other followers