Batch size and compression tuning in Kafka - Mini Project: Build & Apply

Batch Size and Compression Tuning in Kafka Producer

📖 Scenario: You are working on a Kafka producer application that sends messages to a Kafka topic. To improve performance and reduce network usage, you want to tune the batch size and enable compression.This tuning helps in real-world scenarios where sending many small messages individually is slow and costly. Grouping messages into batches and compressing them makes the process faster and more efficient.

🎯 Goal: Build a Kafka producer configuration that sets a specific batch.size and enables compression.type to compress messages before sending.You will create the initial producer configuration, add tuning parameters, implement the producer sending logic, and finally print the configuration to verify your settings.

📋 What You'll Learn

Create a Kafka producer configuration dictionary with basic settings

Add batch.size set to 16384 bytes

Add compression.type set to 'gzip'

Implement a simple message sending loop using the configuration

Print the final producer configuration dictionary

💡 Why This Matters

🌍 Real World

Tuning batch size and compression in Kafka producers helps reduce network load and improve throughput in real-time data pipelines.

💼 Career

Kafka producer tuning is a common task for data engineers and backend developers working with streaming data systems.

1

Create the initial Kafka producer configuration

Create a dictionary called producer_config with these exact entries: 'bootstrap.servers': 'localhost:9092' and 'key.serializer': 'org.apache.kafka.common.serialization.StringSerializer' and 'value.serializer': 'org.apache.kafka.common.serialization.StringSerializer'.

Kafka

# Create the initial Kafka producer configuration dictionary
# Your code here

Hint

Use a Python dictionary with the exact keys and values as shown.

2

Add batch size and compression settings

Add two entries to the producer_config dictionary: 'batch.size' set to 16384 and 'compression.type' set to 'gzip'.

Kafka

producer_config = {
    'bootstrap.servers': 'localhost:9092',
    'key.serializer': 'org.apache.kafka.common.serialization.StringSerializer',
    'value.serializer': 'org.apache.kafka.common.serialization.StringSerializer'
}
# Add batch.size and compression.type to producer_config
# Your code here

Hint

Add the new keys and values inside the existing dictionary.

3

Implement message sending loop

Write a for loop that iterates over range(3) and inside the loop, create a variable message with the value f'Message {i}' where i is the loop variable. (This simulates sending messages.)

Kafka

producer_config = {
    'bootstrap.servers': 'localhost:9092',
    'key.serializer': 'org.apache.kafka.common.serialization.StringSerializer',
    'value.serializer': 'org.apache.kafka.common.serialization.StringSerializer',
    'batch.size': 16384,
    'compression.type': 'gzip'
}
# Write a for loop to simulate sending 3 messages
# Your code here

Hint

Use a for loop with variable i and create the message string inside it.

4

Print the final producer configuration

Write print(producer_config) to display the final producer configuration dictionary.

Kafka

producer_config = {
    'bootstrap.servers': 'localhost:9092',
    'key.serializer': 'org.apache.kafka.common.serialization.StringSerializer',
    'value.serializer': 'org.apache.kafka.common.serialization.StringSerializer',
    'batch.size': 16384,
    'compression.type': 'gzip'
}

for i in range(3):
    message = f'Message {i}'

# Print the producer_config dictionary
# Your code here

Hint

Use print() to show the dictionary exactly.

Practice

1. What does increasing the batch.size setting in Kafka producer configuration primarily affect?

easy

A. The number of bytes sent in one request to the broker

B. The number of partitions a topic has

C. The compression algorithm used for messages

D. The timeout for message delivery

Solution

1. Step 1: Understand batch.size meaning

   The batch.size controls how many bytes the producer will try to batch together before sending to the broker.

2. Step 2: Identify what batch.size affects

   Increasing batch.size means more data is sent in one request, improving throughput but possibly increasing latency.

3. Final Answer:

   The number of bytes sent in one request to the broker -> Option A

4. Quick Check:

   batch.size = bytes per request [OK]

Hint: Batch size controls bytes per request, not partitions or compression [OK]

Common Mistakes:

• Confusing batch size with number of partitions
• Thinking batch size sets compression type
• Assuming batch size controls timeout

2. Which of the following is the correct way to enable compression with gzip in Kafka producer configuration?

easy

A. "compression": "gzip"

B. "compress.type": "gzip"

C. "compression.type": "gzip"

D. "compressionType": "gzip"

Solution

1. Step 1: Recall Kafka producer config keys

   The correct key for compression is compression.type.

2. Step 2: Match correct syntax

   The value should be a string like "gzip". So the correct config is "compression.type": "gzip".

3. Final Answer:

   "compression.type": "gzip" -> Option C

4. Quick Check:

   compression.type = gzip [OK]

Hint: Use exact key 'compression.type' to enable compression [OK]

Common Mistakes:

• Using wrong key names like 'compression' or 'compress.type'
• Incorrect camelCase key 'compressionType'
• Missing quotes around 'gzip'

3. Given the following Kafka producer config snippet:

{
  "batch.size": 16384,
  "compression.type": "snappy"
}

What is the expected effect on message sending?

medium

A. Messages are sent in batches up to 16 KB and compressed with Snappy

B. Messages are sent one by one without compression

C. Messages are compressed with gzip and batch size is ignored

D. Batch size is 16 bytes and compression is disabled

Solution

1. Step 1: Interpret batch.size value

   The batch size is set to 16384 bytes, which means messages will be grouped up to 16 KB before sending.

2. Step 2: Interpret compression.type value

   The compression type is set to "snappy", so messages will be compressed using Snappy algorithm.

3. Final Answer:

   Messages are sent in batches up to 16 KB and compressed with Snappy -> Option A

4. Quick Check:

   batch.size=16384 + compression.type=snappy [OK]

Hint: Check batch size bytes and compression.type value carefully [OK]

Common Mistakes:

• Confusing batch size units (bytes vs KB)
• Assuming gzip compression instead of snappy
• Thinking batch size disables compression

4. You have set batch.size to 0 in your Kafka producer config. What issue will this cause?

medium

A. Producer will throw a configuration error and fail to start

B. Producer will send messages immediately without batching

C. Producer will batch messages indefinitely causing delays

D. Producer will compress messages with default gzip

Solution

1. Step 1: Understand batch.size valid values

   Batch size can be set to 0, which disables batching. Messages are sent immediately without waiting to fill a batch.

2. Step 2: Identify Kafka producer behavior on batch.size=0

   The producer will not throw an error; it will work but send each message in its own request, potentially reducing throughput.

3. Final Answer:

   Producer will send messages immediately without batching -> Option B

4. Quick Check:

   batch.size=0 disables batching [OK]

Hint: batch.size=0 disables batching safely, sends immediately [OK]

Common Mistakes:

• Thinking batch.size=0 causes a configuration error
• Believing it causes indefinite batching and delays
• Confusing batch size with compression settings

5. You want to optimize Kafka producer throughput for large messages but keep latency low. Which combination of settings is best?

hard

A. Use default batch.size and compression.type = "none"

B. Decrease batch.size and disable compression

C. Set batch.size to 0 and use compression.type = "gzip"

D. Increase batch.size and use compression.type = "lz4"

Solution

1. Step 1: Consider batch.size impact on throughput and latency

   Larger batch sizes improve throughput by sending more data at once but can increase latency slightly.

2. Step 2: Choose compression type for speed and size

   LZ4 compression is fast and efficient, reducing message size without high CPU cost, helping throughput and latency.

3. Step 3: Evaluate other options

   Decreasing batch size reduces throughput; disabling compression wastes bandwidth; batch.size=0 causes no batching.

4. Final Answer:

   Increase batch.size and use compression.type = "lz4" -> Option D

5. Quick Check:

   Large batch + fast compression = best throughput & low latency [OK]

Hint: Big batch + fast compression (lz4) balances speed and size [OK]

Common Mistakes:

• Choosing gzip which is slower than lz4
• Setting batch.size to 0 reducing throughput
• Disabling compression reduces efficiency