You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Azure Event Grid吞吐量咨询:每秒可推送及出口事件数

Hey there! Since you're diving into Azure Event Grid for your project implementation, let's break down its throughput capabilities clearly:

每秒可推送的事件数(入口吞吐量)

This refers to the rate at which Event Grid can receive events, with different limits for different topic/source types (most support quota increases):

  • Custom Topics & Domains: The default limit is 1000 events per second (or 1MB/s, whichever is smaller). If your business needs higher throughput, you can submit a quota increase request via the Azure portal, with a maximum achievable limit of 100,000 events per second (or 100MB/s).
  • System Topics (e.g., Storage Account, Blob Storage-triggered events): The entry limit for these topics depends on the corresponding source service. For example, Blob Storage has a default event push limit of 10,000 events per second—specific values can be found in the official quota documentation of the corresponding service.
  • Note: Event size affects actual throughput. If a single event is large (e.g., 2KB), the 1MB/s bandwidth limit will reduce the actual pushable event count to around 500 per second.
每秒出口事件数(输出吞吐量)

Event Grid's outbound throughput isn't a fixed value; it's closely tied to subscription configurations and the processing capacity of your target endpoint:

  • Subscription Concurrency Settings: Each Event Grid subscription has 10 concurrent push connections by default. You can adjust this value in the subscription settings (up to 100), and higher concurrency will increase the number of events output per second.
  • Batch Push Optimization: Event Grid supports packaging multiple events into a single request (each batch can contain up to 1000 events or 1MB in size). Enabling batch push can significantly increase the number of events output per second, provided your target endpoint (e.g., Azure Function, Web App) supports batch event processing.
  • Tier Differences: If you use Event Grid's Premium Tier, you'll get higher outbound performance, lower latency, and more flexible quota adjustment space—ideal for high-throughput business scenarios.
  • Target Endpoint Limits: The final outbound throughput is also limited by the processing capacity of the target service. If your target endpoint can't process requests in a timely manner, Event Grid will retry according to the retry policy, which indirectly affects the actual output rate.

内容的提问来源于stack exchange,提问作者k11k2

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.19 03:08:41