什么是Google Cloud发布/订阅延迟

本文介绍了什么是Google Cloud发布/订阅延迟的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我有一个要求真正低延迟的应用程序(实时游戏). 目前，在我的解决方案中，一条消息从客户端前端服务器路由到目标服务器所需的时间不到2毫秒.

I have an application that requires really low latency (real time game). Currently in my solution it takes less than 2 milliseconds for a message to route to from the client front-end server to the destination server.

有人知道要在Google Cloud Pub/Sub中将消息从一台服务器路由到另一台服务器需要多少时间吗? 谢谢！

Does anybody know how much time will it take in Google Cloud Pub/Sub to route a message from one server to another? Thank you!

推荐答案

虽然Cloud Pub/Sub的端到端延迟为99.9％，对于许多应用程序来说已经足够了，包括一些用于实时交互的应用程序， 2ms低于系统当前的承诺.到目前为止，我们已将高吞吐量和强大的交付保证列为优先事项.端到端延迟也高度取决于订户发出拉取请求的速率.如果吞吐量和/或延迟很重要，则订户应始终至少有几个打开的拉取请求.我们确实旨在大幅减少区域内延迟，但目前Cloud Pub/Sub无法保证第99.9个百分点的2ms区域内延迟.

While Cloud Pub/Sub's end-to-end latency at the 99.9th percentile is sufficient for many applications--including some using it for real-time interaction, 2ms is lower than what the system can currently promise. We have thus far prioritized high throughput and strong delivery guarantees. End-to-end latency is also highly dependent on the rate at which a subscriber issues pull requests. A subscriber should always have at least a few open pull requests if throughput and/or latency are important. We do aim to significantly reduce out intra-region latencies but at the moment Cloud Pub/Sub cannot guarantee 2ms intra-region latencies at the 99.9th percentile.