Understanding the latency benefits of multi-cloud webservice deployments

Understanding the latency benefits of multi-cloud webservice deployments
复制标题

DOI:
10.1145/2479957.2479960
复制
发表时间:
2013-04
期刊:
Comput. Commun. Rev.
影响因子:
--
通讯作者:
Zhe Wu;H. Madhyastha
Zhe Wu;H. Madhyastha
中科院分区:
其他
文献类型:
--
作者:
Zhe Wu;H. Madhyastha

文献摘要

被引文献

相似文献

为了最大限度地减少用户感知的延迟,Web服务通常部署在多个地理分布的数据中心。我们工作的前提是,部署在多个云基础设施服务上的Web服务可以为来自更多数据中心的用户提供服务,而不是使用单个云服务,因此,为用户提供更低的延迟。在本文中,我们进行了全面的测量研究,以了解在三种流行的云基础设施服务- Amazon EC2,Google Compute Engine(GCE)和Microsoft Azure上部署Web服务的潜在延迟优势。我们估计,与部署在其中一个云服务上相比,当跨三个云服务部署Web服务时,IP地址前缀多达一半的用户可以将其RTT减少20%以上。当我们深入了解这些延迟的好处时,我们有三个重要的观察结果。首先,当Web服务从单云部署转移到多云部署时,很大一部分前缀将通过从同一位置的不同数据中心提供服务而获得延迟优势。这是因为存在于一个云服务中的前缀与附近数据中心之间的路由低效在从前缀到不同云服务中的附近数据中心的路径上不存在。第二,尽管大部分前缀将感知到延迟改进,但是在几个位置(例如,阿根廷和以色列)将继续产生大于100毫秒的RTT,即使Web服务跨越三个大规模云服务(EC2,GCE和Azure)。最后,我们看到,利用多云部署提供的延迟优势在实践中可能具有挑战性;我们的测量显示,为前缀提供最低延迟的数据中心通常在不同的云服务之间波动,因此需要复制数据。
To minimize user-perceived latencies, webservices are often deployed across multiple geographically distributed data centers. The premise of our work is that webservices deployed across multiple cloud infrastructure services can serve users from more data centers than that possible when using a single cloud service, and hence, offer lower latencies to users. In this paper, we conduct a comprehensive measurement study to understand the potential latency benefits of deploying webservices across three popular cloud infrastructure services - Amazon EC2, Google Compute Engine (GCE), and Microsoft Azure. We estimate that, as compared to deployments on one of these cloud services, users in up to half the IP address prefixes can have their RTTs reduced by over 20% when a webservice is deployed across the three cloud services. When we dig deeper to understand these latency benefits, we make three significant observations. First, when webservices shift from single-cloud to multi-cloud deployments, a significant fraction of prefixes will see latency benefits simply by being served from a different data center in the same location. This is because routing inefficiencies that exist between a prefix and a nearby data center in one cloud service are absent on the path from the prefix to a nearby data center in a different cloud service. Second, despite the latency improvements that a large fraction of prefixes will perceive, users in several locations (e.g., Argentina and Israel) will continue to incur RTTs greater than 100ms even when webservices span three large-scale cloud services (EC2, GCE, and Azure). Finally, we see that harnessing the latency benefits offered by multi-cloud deployments is likely to be challenging in practice; our measurements show that the data center which offers the lowest latency to a prefix often fluctuates between different cloud services, thus necessitating replication of data.