作为受管系统服务的远程过程调用
Remote Procedure Call as a Managed System Service
AI总结:
本文提出 mRPC 系统,将 RPC 编组与策略执行从应用内库下沉为受管系统服务,在提升微服务性能(DeathStarBench 最高 2.5 倍加速)的同时支持透明在线升级,兼顾策略灵活性与可用性。
摘要:
远程过程调用(RPC)是云计算中广泛使用的抽象。程序员为每个远程过程指定类型信息,编译器生成链接到每个应用程序的桩代码,用于将参数编组和解组到消息缓冲区中。然而,应用程序和服务运维团队越来越需要对服务之间 RPC 流的高可见性和控制能力,这导致许多部署使用边车(sidecar)或服务网格代理来实现可管理性和策略灵活性。这些边车通常涉及对桩编译器刚刚精心组装好的 RPC 数据进行检查和修改,增加了不必要的开销。此外,升级多样化的应用程序 RPC 桩以使用 RDMA 或 DPDK 等高级硬件能力是一个漫长而复杂的过程,并且常常与边车策略控制不兼容。在本文中,我们提出、实现并评估了一种新颖的方法,其中 RPC 编组和策略执行作为系统服务完成,而不是作为链接到每个应用程序的库。应用程序像以前一样向 RPC 系统指定类型信息,而 RPC 服务执行策略引擎并仲裁资源使用,然后根据底层网络硬件能力定制编组数据。我们的系统 mRPC 还支持在线升级,使得策略和编组代码都能对应用程序代码透明地更新。与使用边车相比,mRPC 将标准微服务基准 DeathStarBench 的速度提高了最多 2.5 倍,同时具有更高的策略灵活性和可用性。
英文摘要:
Remote Procedure Call (RPC) is a widely used abstraction for cloud computing. The programmer specifies type information for each remote procedure, and a compiler generates stub code linked into each application to marshal and unmarshal arguments into message buffers. Increasingly, however, application and service operations teams need a high degree of visibility and control over the flow of RPCs between services, leading many installations to use sidecars or service mesh proxies for manageability and policy flexibility. These sidecars typically involve inspection and modification of RPC data that the stub compiler had just carefully assembled, adding needless overhead. Further, upgrading diverse application RPC stubs to use advanced hardware capabilities such as RDMA or DPDK is a long and involved process, and often incompatible with sidecar policy control. In this paper, we propose, implement, and evaluate a novel approach, where RPC marshalling and policy enforcement are done as a system service rather than as a library linked into each application. Applications specify type information to the RPC system as before, while the RPC service executes policy engines and arbitrates resource use, and then marshals data customized to the underlying network hardware capabilities. Our system, mRPC, also supports live upgrades so that both policy and marshalling code can be updated transparently to application code. Compared with using a sidecar, mRPC speeds up a standard microservice benchmark, DeathStarBench, by up to 2.5$\times$ while having a higher level of policy flexibility and availability.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。