Skip to content

Commit ce43e80

Browse files
authored
Update brokered connection example in event-hubs-tier-limits.md
Updated the example under "Number of brokered connections per namespace" to better fit the scaling of Event Hub Premium (from 3 to 4). As per https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-scalability#processing-units "You can purchase 1, 2, 4, 6, 8, 10, 12, or 16 processing Units for each Event Hubs Premium namespace"
1 parent 85dac30 commit ce43e80

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/event-hubs/includes/event-hubs-tier-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The following table shows limits that are different for Basic, Standard, Premium
2222
| Maximum size of Event Hubs publication | 256 KB | 1 MB | 1 MB | 1 MB |
2323
| Number of consumer groups per event hub | 1 | 20 | 100 | 1,000<br/>No limit per CU |
2424
| Number of Kafka consumer groups per namespace | NA | 1,000 | 1,000 | 1,000 |
25-
| Number of brokered connections per namespace | 100 | 5,000 | 10,000 per PU<br/><br/>For example, if the namespace is assigned 3 PUs, the limit is 30,000. | 100,000 per CU |
25+
| Number of brokered connections per namespace | 100 | 5,000 | 10,000 per PU<br/><br/>For example, if the namespace is assigned 4 PUs, the limit is 40,000. | 100,000 per CU |
2626
| Maximum retention period of event data | 1 day | 7 days | 90 days | 90 days |
2727
| Event storage for retention | 84 GB per TU | 84 GB per TU | 1 TB per PU | 10 TB per CU |
2828
| Maximum TUs or PUs or CUs | 40 TUs | 40 TUs | 16 PUs | 20 CUs |

0 commit comments

Comments
 (0)