...
Test Name | No Load (events/sec) | 500 AVC events/sec | % Loss | 1000 AVC events/sec | % Loss |
|---|---|---|---|---|---|
Legacy Batch Read | 116 | 110 | -5.5% | 107 | -8.1% |
Analysis:
Unlike search and write operations, legacy Legacy batch read performance improves declines under load, showing with a 5.5% gain decrease at 500 AVC events/sec and an 8.1% gain decrease at 1,000 AVC events/sec. This indicates that as the system experiences more AVC events, the efficiency of batch read operations is negatively impacted. The increasing loss suggests that higher event rates introduce processing overhead, potentially due to resource contention, increased latency, or queuing delays. These factors may contribute to slower response times and reduced throughput for batch read operations under heavy system load.
Conclusion & Recommendations
...
Yes, using a single Kafka partition is likely affecting event processing, especially under high event rates (500 or 1,000 AVC events/sec). Scaling partitions and optimizing consumer settings can help mitigate performance issues. 🚀
Notes: How to check kafka configuration of CPS ?
Checking in Kafka Configuration (For Default Settings)
If you haven't explicitly set the number of partitions while creating the topic, Kafka may use the default partition count from the broker settings.
To check Kafka's default number of partitions, run:
| Code Block | ||
|---|---|---|
| ||
cat /etc/kafka/server.properties | grep num.partitions |
Example Output:
| Code Block |
|---|
num.partitions=1 |
num.partitions=1
If it's 1, all newly created topics will have a single partition by default unless overridden.
This image confirms that Kafka is configured with a single partition (
num.partitions=1) into CPS.
...