MSE ZooKeeper Enterprise Edition supports a Service-Level Agreement (SLA) of 99.99% and delivers twice the performance of open source ZooKeeper. It provides higher quotas using dedicated core resources. This topic describes the capacity thresholds and performance benchmarks for different specifications of ZooKeeper Enterprise Edition.
Capacity thresholds
Connections: The number of connections established between ZooKeeper clients and the ZooKeeper server. In most scenarios, one pod establishes one connection.
Number of watches: The number of watches set by ZooKeeper clients on the ZooKeeper server.
Storage size: The total size of data that ZooKeeper clients store on the ZooKeeper server. You can approximate this value based on the size of the snapshot file generated by the server.
The following table describes the capacity metrics of a single node.
Specification | Number of nodes | Connections | Storage size limit | Number of watches | |||
Safe level | Warning level | Safe level | Warning level | Safe level | Warning level | ||
Small.Platinum.x2 | 1 | 1,320 | 2,000 | 66 MB | 100 MB | 660 W | 10,000,000 |
Medium.Platinum.x1 | 1 | 2,640 | 4,000 | 330 MB | 500 MB | 13,200,000 | 20,000,000 |
Medium.Platinum.x2 | 1 | 5,280 | 8,000 | 660 MB | 1 GB | 2,640 W | 40,000,000 |
Large.Platinum.x1 | 1 | 10,560 | 16,000 | 1,320 MB | 2 G | 5280 W | 80,000,000 |
The number of connections and the number of watches are capacity limits for a single node. For a three-node cluster, the total capacity is three times the single-node capacity specified in the preceding table.
The storage size limit applies to the entire cluster. For a three-node cluster, this limit is the value specified in the preceding table.
If the capacity limit is exceeded, throttling is triggered.