Report Benchmarks Public Cloud Providers’ Performance
SAN FRANCISCO—Location, location, location. It’s not just important for real estate but also for public cloud performance. That’s the conclusion of a recently published Public Cloud Performance Benchmark Report from network monitoring firm ThousandEyes.
Imagine you’re building out an internationally-based enterprise IoT project that will leverage infrastructure from one of the top three public cloud providers: Amazon Web Services, Microsoft Azure and Google Cloud Platform and you would like to spread computing across multiple regions. Although it is difficult to crown any of the big three as a winner (or loser) in terms of network reliability, the report finds clear differences in performances in specific regions.
For instance, Europe-based GCP users who need to send data to Mumbai must contend with three times the latency compared to the other two options. That delay is a result of the circuitous route GCP uses to send traffic from continental Europe to the United Kingdom and finally to a backbone in the United States before it reaches India. GCP also has roughly three times as much latency when linking Mumbai and Europe.
But if you plan to use Microsoft Azure in Brazil, the bidirectional latency you encounter will be four times slower than AWS and nearly eight times slower than GCP.
Conversely, if your public cloud use is based in Europe or North America, AWS, Azure and GCP have broadly similar network performance.
Apart from these regional differences, one of the most significant findings from the ThousandEyes study is that AWS is more prone to performance-related problems. That’s because the Amazon service routes traffic through the internet, which is generally more volatile. “AWS loves the internet, but the internet doesn’t love AWS back,” quipped report author Archana Kesavan, senior product marketing manager at ThousandEyes. This fact also tends to make AWS performance suffer in world regions with poor internet connectivity. That can be problematic in Asia, for instance, where internet fiber routes are less common than in, say, Europe or North America. AWS is thus 30 percent less stable in Asia than the other two providers, which ingest user traffic closer to the user location.
Although the ThousandEyes report stopped short in declaring a winner among the three cloud providers in its report, Azure tended to fare best overall in terms of reliability.
Another important consideration is the architecture of the apps running on top of the public cloud. “To me, [the conclusion of the report] was not so much about how you make a decision about which cloud provider to use, it was how you use this data to understand performance and the architecture of network traffic once you are already investing in services,” said Paul Chapman, chief information officer of Box in a discussion at the ThousandEyes event announcing the results. “You don’t have control over when it comes to data residency and compliance and regulatory [considerations] that influence where services run.”
“You do have to get comfortable with the provider if you are going to go with the public cloud. You need to understand what you are getting into. It is not turnkey. You have to understand the topologies, how to deploy your services and how to deploy your firewalls,” said Kira Makagon, executive vice president of innovation at RingCentral at the aforementioned event. “It is not like I just get the network with the pairing with the internet providers and I am done. You have to decide which services to use.”
The report also revealed that the three companies use provider backbone networks for traffic passing from one cloud provider to another. A growing number of companies rely on multi-cloud arrangements with some doing so unknowingly. For instance, an enterprise using Azure and Slack would rely on cloud connectivity from two providers, since Slack is hosted on AWS. The connectivity among the three public cloud providers bodes well for such arrangements.
For now, ThousandEyes counsels that organizations planning to leverage public cloud connectivity should take into consideration regional performance data while evaluating a multi-cloud strategy to compensate for sub-optimal performance from an organization’s central provider. The company also recommends that organizations gather ongoing performance data.
Ultimately, the cloud is constantly evolving and it is entirely possible that, next year, the performance of the big three will vary considerably. ThousandEyes is already planning a sequel to this report next year.