事件网格吞吐量限制 [英] Event grid throughput limit

查看:98
本文介绍了事件网格吞吐量限制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是天蓝色的事件网格概念的新手,目前正在研究事件网格以在我们的项目中实施. 谁能说出事件网格的吞吐量, 我每秒可以推送多少个事件,每秒事件网格的输出是多少,意味着每秒从事件网格输出的事件数.

I'm new to azure event grid concepts and currently doing research on event grid to implement in our project. Can any one tell about the throughput of event grid, how many events I can push per second and what is the egress of event grid per second, means count of output events per second from event grid.

推荐答案

我向微软询问了这个主题,这是他们的回应:

I asked Microsoft about this topic and this was their response:

Nape: 发布速率限制约为每秒5000个事件.这是您可以发布到事件网格的事件.如果未加载服务实例,则可以获得比此更高的速率.请记住,EG是一个多租户系统.

Nape: Publish rate limit is about 5000 events per second. This is the events you can publish to Event Grid. You can achieve rates higher than this if the service instance is not as loaded. Keep in mind EG is a multitenant system.

https://docs.microsoft.com/zh-CN/azure/iot-hub/iot-hub-event-grid-routing-comparison 高:每个区域每秒可以路由10,000,000个事件.

https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-event-grid-routing-comparison High: Capable of routing 10,000,000 events per second per region.

上方表示整个服务在每个区域中调度事件的能力.

Above represents the capability of the entire service in dispatching events, per region.

这篇关于事件网格吞吐量限制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆