Skip to content

Instantly share code, notes, and snippets.

@weltonrodrigo
Last active July 21, 2022 13:15
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save weltonrodrigo/3e75528f42e33711ae974d3af9111e0d to your computer and use it in GitHub Desktop.
Save weltonrodrigo/3e75528f42e33711ae974d3af9111e0d to your computer and use it in GitHub Desktop.
Azure eventhub auto-inflates only on ingress, not egress

Does eventhub auto-inflates on egress?

No.


Yeah, that took me a long time.

The ingress rate is what makes the eventhub namespace scale, but not the consumption (the egress). Egress don't get throttled either, you'll have to keep an eye at the rate of consumption and partition limits.

One partition can handle 1MB/s traffic (ingress and egress), so ~500Kb ingress (with you have only one consumer group on that partition).

Each TU gives you 1MB/s ingress and 2MB/s egress over the whole namespace and all partitions.

If you hit too much the ingress limit posed by the reserved TU, the namespace will scale up to the configured maximum.

But if you hit the egress, that won't happen. You'll probably won't even realize that you consumption is hitting the partition maximum or the namespace maximum, you'll have to calculate that yourself.

At this doc:

Event Hubs is launching the new Auto-Inflate feature, which enables you to scale-up your TUs automatically to meet your usage needs. This simple opt-in feature gives you the control to prevent throttling when, data ingress rates exceed your pre-determined TUs and when your egress rates exceed your set TUs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment