Before you roll out your Kafka client applications to the production, you can and should benchmark and optimize your applications based on your application’s SLAs to tune and optimize performance.

​

Benchmarking

Benchmark testing is essential because there is no one-size-fits-all configuration for Kafka applications. The optimal configuration depends on your specific use case, enabled features, data profile, and other factors. You should run benchmark tests when planning to tune Kafka clients beyond the default settings. Understanding your application’s performance profile is crucial, especially when choosing the right data streaming engine and optimizing for throughput or latency. Benchmark test results can also help determine the right size of your StreamNative Cloud cluster and the appropriate number of partitions and producer/consumer processes.

​

Initial Performance Baseline

Start by measuring baseline performance using:

• Kafka tools kafka-producer-perf-test and kafka-consumer-perf-test that are bundled in the Kafka distribution for JVM clients
• rdkafka_performance interface for non-JVM clients using librdkafka

These tools provide a baseline performance measurement without application logic. Note that these performance tools do not support Schema Registry.

​

Application Testing

1. Test your application using default Kafka configuration parameters first

2. Establish producer baseline performance:

   • Remove upstream dependencies
   • Use mock data generation or sanitized production data
   • Ensure test data reflects production data characteristics
   • When testing with compression, be mindful that unrealistic mock data (repeated patterns, zero padding) may show better compression than production data

3. Producer benchmarking:

   • Start with a single producer on one server
   • Measure throughput using producer metrics
   • Incrementally increase producer processes to find optimal count per server

4. Consumer benchmarking:

   • Follow similar process as producer testing
   • Start with single consumer, then increase processes
   • Determine optimal number of consumer processes per server

​

Tuning Process

1. Run benchmark tests with different configuration parameters aligned with your application’s SLAs
2. Focus on a subset of parameters - avoid changing defaults without understanding system impact
3. Iterate through: adjust settings, test, analyze results, and repeat
4. Continue until meeting throughput and latency requirements

​

Defining Application SLAs

While getting a Kafka client application running is relatively quick, proper tuning is essential before production deployment. Different use cases have different requirements, so you must identify your primary service goals and align them with your application’s SLAs. For a modern cloud data streaming platform, it is impossible to achieve all three properties of Cost, Availability, and Performance based on the New CAP Theorem, so you need to find the right balance among them.

• Throughput
• Latency
• Durability
• Availability

​

Considerations

Consider these factors when determining service goals to align with your application’s SLAs:

1. The specific use cases your Kafka applications serve
2. Critical application and business requirements
3. Kafka’s role in your business applications and services

Before tuning your Kafka client application, it’s crucial to discuss business requirements and goals with your team to determine which metrics to optimize. There are two key reasons for this:

First, there are inherent trade-offs between different performance goals. You cannot simultaneously maximize throughput, latency, durability, and availability. For example, improving throughput often comes at the cost of increased latency, while maximizing durability can impact availability. While optimizing one metric doesn’t completely sacrifice the others, these goals are interconnected and require careful balance.

Second, identifying your applications SLAs helps guide Kafka configuration tuning. By understanding user expectations, you can optimize the system appropriately. Consider which of these goals is most important for your use case:

High Throughput (maximizing data movement rate):

• Best for: High-volume data processing applications that need to handle millions of writes per second
• Example: Log aggregation systems, batch processing pipelines

Low Latency (minimizing end-to-end message delivery time):

• Best for: Real-time applications requiring immediate data delivery
• Examples: Chat applications, interactive websites, IoT device monitoring

High Durability (ensuring no data loss):

• Best for: Systems where data integrity is critical
• Examples: Financial transactions, audit logging, event sourcing systems

High Availability (maximizing uptime):

• Best for: Mission-critical applications that cannot tolerate downtime
• Examples: Payment processing systems, user authentication services