Test Results
| Partitions | Replicas | Synchronous Replication Enabled | batch.size | Cross-AZ Production | Message Production Rate on the Client Side (Records/Second) | CPU Usage on the Server Side (broker-0) | CPU Usage on the Server Side (broker-1) | CPU Usage on the Server Side (broker-2) |
|---|---|---|---|---|---|---|---|---|
| 3 | 1 | No | 1 KB | No | 27,417 | 57% | 58% | 58% |
| 3 | 1 | No | 16 KB | No | 102,399 | 31% | 33% | 31% |
| 3 | 1 | No | 1 KB | Yes | 15,351 | 37% | 39% | 36% |
| 3 | 3 | Yes | 1 KB | No | 3859 | 62% | 62% | 60% |
| 3 | 3 | No | 1 KB | No | 11,558 | 89% | 88% | 87% |
Based on the test results, the following conclusions are drawn (for reference only):
- When the batch.size of production requests is 16 times larger, the message production rate increases, and the CPU usage decreases.
- Compared with cross-AZ production, intra-AZ production significantly increases message production rate and CPU usage.
- When the number of replicas changes from 1 to 3, the message production rate decreases significantly, and the CPU usage increases.
- Compared with synchronous replication, asynchronous replication increases the message production rate and the CPU usage.