Skip to content

Commit fdb6b63

Browse files
Merge pull request #288733 from jaganth/docs-editor/event-hubs-premium-overview-1729275269
Update event-hubs-premium-overview.md
2 parents 4c39d3e + 3ec91d7 commit fdb6b63

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/event-hubs/event-hubs-premium-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ In addition to these storage-related features and all capabilities and protocol
1717
> - Event Hubs Premium supports TLS 1.2 or greater.
1818
> - The Premium tier isn't available in all regions. Try to create a namespace in the Azure portal. See the supported regions in the **Location** dropdown list on the **Create Namespace** page.
1919
20-
You can purchase 1, 2, 4, 8, and 16 processing units (PUs) for each namespace. Because the Premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle like it is in the Standard tier. The throughput depends on the work you ask Event Hubs to do, which is similar to the Dedicated tier. The effective ingest and stream throughput per PU depends on various factors, such as the:
20+
You can purchase 1, 2, 4, 6, 8, 10, 12, and 16 processing units (PUs) for each namespace. Because the Premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle like it is in the Standard tier. The throughput depends on the work you ask Event Hubs to do, which is similar to the Dedicated tier. The effective ingest and stream throughput per PU depends on various factors, such as the:
2121

2222
* Number of producers and consumers.
2323
* Payload size.

0 commit comments

Comments
 (0)