Skip to content

Commit a22ec19

Browse files
authored
Update event-hubs-premium-overview.md
1 parent ed77706 commit a22ec19

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ It replicates events to three replicas, distributed across Azure availability zo
1414
In addition to these storage-related features and all capabilities and protocol support of the standard tier, the isolation model of the premium tier enables features like [dynamic partition scale-up](dynamically-add-partitions.md). You also get far more generous [quota allocations](event-hubs-quotas.md). Event Hubs Capture is included at no extra cost.
1515

1616
> [!NOTE]
17-
> Event Hubs Premium supports TLS 1.2 or greater .
17+
> Event Hubs Premium supports TLS 1.2 or greater.
1818
1919
## Why premium?
2020
The premium tier offers three compelling benefits for customers who require better isolation in a multitenant environment with low latency and high throughput data ingestion needs.
@@ -41,7 +41,7 @@ Therefore, the premium tier is often a more cost effective option for event stre
4141

4242
For the extra robustness gained by availability-zone support, the minimal deployment scale for the dedicated tier is 8 capacity units (CU), but you'll have availability zone support in the premium tier from the first PU in all availability zone regions.
4343

44-
You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it's' in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
44+
You can purchase 1, 2, 4, 8 and 16 processing units for each namespace. As the premium tier is a capacity-based offering, the achievable throughput isn't set by a throttle as it is in the standard tier, but depends on the work you ask Event Hubs to do, similar to the dedicated tier. The effective ingest and stream throughput per PU will depend on various factors, including:
4545

4646
* Number of producers and consumers
4747
* Payload size

0 commit comments

Comments
 (0)