This document provides performance test data for EventBridge event streams in various scenarios. You can use this data to assess and plan resource configurations for event stream tasks.
This test is optimized for low latency. If your scenario prioritizes throughput and is not sensitive to latency, the actual performance may be better.
Performance testing from a Kafka topic to a Kafka topic
Test environment configuration
Kafka instance specifications
Configuration item | Upstream instance | Downstream instance |
Specification type | Standard Edition (High-write) | Standard Edition (High-write) |
Instance type | Internet- and VPC-connected instance | Internet- and VPC-connected instance |
Traffic specification | alikafka.hw.2xlarge Peak read traffic 20 MB/s Peak write traffic 20 MB/s | alikafka.hw.2xlarge Peak read traffic 20 MB/s Peak write traffic 20 MB/s |
Internet traffic | 81 Mbps | 81 Mbps |
Disk type | Ultra disk | Ultra disk |
Disk capacity | 900 GB Storage capacity 300 GB Backup capacity 600 GB | 900 GB Storage capacity 300 GB Backup capacity 600 GB |
Version | 2.6.2 | 2.6.2 |
Topic category | Normal message | Normal message |
Message size | 1 KB | 1 KB |
Message content | Key: null Body: Random string | Key: null Body: Random string |
Event stream task parameters
Source configuration
Parameter | Value |
Network configuration | Classic Network |
Data format | Binary |
Sink configuration
Parameter | Value |
Acknowledgment mode (ack) | None |
Message body (Value) | Binary extraction: $.data.value |
Message key (Key) | $.data.key |
Advanced configuration
Parameter | Value |
Batch push size | 100 |
Batch push interval (seconds) | 0 |
Test method
A producer is configured to write data to the source Kafka instance. The following batch sending parameters are used:
Maximum batch wait time: 50 ms
Batch sending window: 100 messages
Test results
Minimum CUs | Maximum CUs | Event processing rate (events/s) | Throughput (MB/s) | Latency (ms) |
1 | 1 | 1,500 | 1.5 | 70-80 |
2 | 2 | 4,000 | 4 | 70-90 |
3 | 3 | 6,000 | 6 | 80-100 |
4 | 4 | 8,000 | 8 | 80-120 |
The following factors significantly affect event stream performance:
Producer batch sending: Disabling batch sending reduces the processing capability of a Capacity Unit (CU) by about 50%.
Message size: Large individual messages reduce CU processing capability.
Event stream batch configuration: Disabling the batch push window reduces CU processing capability.
Downstream response time: High downstream response latency reduces CU processing capability.
Data format: Using the JSON format reduces CU processing capability. The more complex the structure, the greater the impact.
Message compression: Using message compression on the source Kafka instance reduces CU processing capability.
Performance testing from a RocketMQ topic to a RocketMQ topic
Test environment configuration
RocketMQ instance specifications
Configuration item | Upstream instance | Downstream instance |
Main series | Platinum Edition | Platinum Edition |
Sub-series | Cluster High-availability Edition | Cluster High-availability Edition |
Instance version | 5.0-rmq-20250410-1 | 5.0-rmq-20250410-1 |
Instance type | rmq.u2.10xlarge | rmq.u2.10xlarge |
Public bandwidth | Fixed bandwidth 51 Mb/s | Fixed bandwidth 10 Mb/s |
Peak transactions per second (TPS) for sending/receiving | 5,000 for sending / 5,000 for receiving | 5,000 for sending / 5,000 for receiving |
Peak elastic TPS for sending/receiving | 10,000 for sending / 10,000 for receiving | 2,500 for sending / 2,500 for receiving |
Topic category | Normal message | Normal message |
Message size | 1 KB | 1 KB |
Message content | Properties: System default Body: Random string | Properties: System default Body: Random string |
Event stream task parameters
Source configuration
Parameter | Value |
RegionId | cn-hangzhou |
InstanceId | rmq-cn-xxx |
Topic | test_perf |
GroupID | GID_EVENTBRIDGE_xxx |
InstanceType | Cloud_5 |
InstanceVpcId | vpc-xxx |
InstanceVSwitchIds | vsw-xxx |
InstanceSecurityGroupId | sg-xxx |
InstanceNetwork | PrivateNetwork |
Sink configuration
Parameter | Configuration |
InstanceId | Value: "rmq-cn-xxx", Form: "CONSTANT" |
Topic | Value: "test_perf", Form: "CONSTANT" |
Body | Value: "$.data.body", Form: "BINARY_EXTRACTION" |
Properties | Value: "{\"userProperties\":\"$.data.userProperties\",\"msgId\":\"$.data.systemProperties.UNIQ_KEY\"}" Form: "TEMPLATE" Template: "{\"EB_SYS_EMBED_OBJECT\":\"${userProperties}\",\"UNIQ_KEY\":\"${msgId}\"}" |
Keys | Value: "$.data.systemProperties.KEYS", Form: "JSONPATH" |
Tags | Value: "$.data.systemProperties.TAGS", Form: "JSONPATH" |
InstanceType | Value: "SelfBuilt", Form: "CONSTANT" |
VpcId | Value: "vpc-xxx", Form: "CONSTANT" |
VSwitchIds | Value: "vsw-xxx", Form: "CONSTANT" |
SecurityGroupId | Value: "sg-xxx", Form: "CONSTANT" |
InstanceUsername | Value: "xxx", Form: "CONSTANT" |
InstancePassword | Value: "xxx", Form: "CONSTANT" |
DeliveryOrderType | Value: "Concurrently", Form: "CONSTANT" |
Network | Value: "PrivateNetwork", Form: "CONSTANT" |
InstanceEndpoint | Value: "rmq-cn-xxx-vpc.cn-hangzhou.rmq.aliyuncs.com:8080", Form: "CONSTANT" |
Advanced configuration
Parameter | Value |
ErrorsTolerance | NONE |
RetryStrategy | PushRetryStrategy: "EXPONENTIAL_DECAY_RETRY" |
BusinessOption | BusinessMode: "CapacityUnitMode" MaxCapacityUnitCount: "4" MinCapacityUnitCount: "4" |
Test method
In this test, 1 KB messages with random content are sent individually to the upstream topic.
Test results
Minimum CUs | Maximum CUs | Event processing rate (events/s) | Latency (ms) |
1 | 1 | 500 | About 150 |
2 | 2 | 1,000 | 110-180 |
3 | 3 | 1,500 | 125-218 |
4 | 4 | 2,000 | 140-218 |