云微服务的集体自动缩放
Collective Autoscaling for Cloud Microservices
摘要:
随着云应用程序从单体转向松散耦合的微服务,应用程序开发人员必须决定有多少计算资源(例如,复制容器的数量)分配给应用程序中的每个微服务。这一决定会影响(1)应用程序开发人员的美元成本和(2)应用程序用户感知的端到端延迟。如今,当每个微服务的CPU或内存利用率超过可配置的阈值时,通过添加VM来独立地自动扩展各个微服务。然而,应用程序用户的端到端延迟包括在多个微服务上花费的时间,每个微服务可能需要不同数量的VM来实现整体端到端延迟。我们提出了COLA,一个基于微服务的应用程序的自动缩放器,它将VM集体分配给微服务,其全球目标是最小化美元成本,同时将端到端应用程序延迟保持在给定目标下。使用5个开源应用程序,我们将COLA与几种利用率和基于机器学习的自动缩放器进行了比较。我们在Google Kubernetes Engine(GKE)上的不同计算设置中评估COLA,其中用户管理计算资源,GKE标准,以及云提供商管理计算基础设施的新操作模式,GKE Autopilot。COLA在63个工作负载中的53个上达到了预期的中位或尾部延迟目标,与下一个最便宜的自动定标器相比,平均成本降低了19.3%。COLA是这53种工作负载中48种最具成本效益的自动扩展策略。使用COLA管理集群节省的成本使COLA在几天内就能支付培训费用。在较小的应用程序中,我们可以彻底搜索微服务配置,我们发现COLA在90%的情况下是最佳的,在其他情况下接近最佳。
英文摘要:
As cloud applications shift from monoliths to loosely coupled microservices, application developers must decide how many compute resources (e.g., number of replicated containers) to assign to each microservice within an application. This decision affects both (1) the dollar cost to the application developer and (2) the end-to-end latency perceived by the application user. Today, individual microservices are autoscaled independently by adding VMs whenever per-microservice CPU or memory utilization crosses a configurable threshold. However, an application user's end-to-end latency consists of time spent on multiple microservices and each microservice might need a different number of VMs to achieve an overall end-to-end latency. We present COLA, an autoscaler for microservice-based applications, which collectively allocates VMs to microservices with a global goal of minimizing dollar cost while keeping end-to-end application latency under a given target. Using 5 open-source applications, we compared COLA to several utilization and machine learning based autoscalers. We evaluate COLA across different compute settings on Google Kubernetes Engine (GKE) in which users manage compute resources, GKE standard, and a new mode of operation in which the cloud provider manages compute infrastructure, GKE Autopilot. COLA meets a desired median or tail latency target on 53 of 63 workloads where it provides a cost reduction of 19.3%, on average, over the next cheapest autoscaler. COLA is the most cost effective autoscaling policy for 48 of these 53 workloads. The cost savings from managing a cluster with COLA result in COLA paying for its training cost in a few days. On smaller applications, for which we can exhaustively search microservice configurations, we find that COLA is optimal for 90% of cases and near optimal otherwise.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。