Producer throughput optimization in Kafka - Mini Project: Build & Apply

Producer throughput optimization

📖 Scenario: You are working with Apache Kafka to send messages from a producer to a topic. To improve how fast your producer sends messages, you want to optimize the throughput by adjusting some settings.

🎯 Goal: Build a Kafka producer configuration that optimizes throughput by setting batch size and linger time, then send a batch of messages and print a confirmation.

📋 What You'll Learn

Create a Kafka producer configuration dictionary with specific settings

Add a batch size setting to control message batching

Add a linger.ms setting to delay sending to increase batch size

Send multiple messages using the producer

Print a confirmation message after sending

💡 Why This Matters

🌍 Real World

Optimizing Kafka producer throughput helps in real-time data pipelines where sending messages quickly and efficiently is important.

💼 Career

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

1

Create Kafka producer configuration

Create a dictionary called producer_config with these exact entries: bootstrap.servers set to "localhost:9092" and acks set to "all".

Kafka

# Create the producer_config dictionary with bootstrap.servers and acks
# Your code here

Hint

Use a Python dictionary with keys as strings and values as strings.

2

Add batch size setting

Add a new entry to producer_config with key batch.size and value 16384 (an integer).

Kafka

producer_config = {
    "bootstrap.servers": "localhost:9092",
    "acks": "all"
}
# Add batch.size to producer_config
# Your code here

Hint

Remember to add a comma after the previous entry.

3

Add linger.ms setting

Add a new entry to producer_config with key linger.ms and value 5 (an integer).

Kafka

producer_config = {
    "bootstrap.servers": "localhost:9092",
    "acks": "all",
    "batch.size": 16384
}
# Add linger.ms to producer_config
# Your code here

Hint

Adding linger.ms helps the producer wait a bit to batch more messages.

4

Send messages and print confirmation

Using the producer_config, create a Kafka producer object called producer. Then send three messages with keys "key1", "key2", "key3" and values "message1", "message2", "message3" to the topic "test-topic". Finally, print "Messages sent successfully".

Kafka

producer_config = {
    "bootstrap.servers": "localhost:9092",
    "acks": "all",
    "batch.size": 16384,
    "linger.ms": 5
}
# Create producer and send messages
# Your code here

Hint

Use Producer from confluent_kafka, call produce for each message, then flush() to send all.

Practice

1. What is the main benefit of increasing the batch.size setting in a Kafka producer?

easy

A. It guarantees message delivery to all replicas.

B. It compresses messages to save disk space.

C. It allows sending more messages together, improving throughput.

D. It reduces the number of partitions in a topic.

Solution

1. Step 1: Understand batch.size role

   The batch.size controls how many messages the producer groups before sending.

2. Step 2: Effect on throughput

   Grouping more messages reduces network calls, increasing throughput.

3. Final Answer:

   It allows sending more messages together, improving throughput. -> Option C

4. Quick Check:

   batch.size increases throughput [OK]

Hint: More batch size means fewer sends, better throughput [OK]

Common Mistakes:

• Confusing batch.size with message compression
• Thinking batch.size controls message durability
• Assuming batch.size changes topic partitions

2. Which of the following is the correct way to set the linger time to 100 milliseconds in Kafka producer configuration?

easy

A. "linger.ms = 100"

B. "linger_time = 100"

C. "lingerMs: 100"

D. "linger = 100ms"

Solution

1. Step 1: Identify correct property name

   The Kafka producer uses linger.ms to set linger time in milliseconds.

2. Step 2: Confirm correct syntax

   The correct syntax is linger.ms = 100, using dot notation and milliseconds.

3. Final Answer:

   "linger.ms = 100" -> Option A

4. Quick Check:

   linger.ms sets linger time [OK]

Hint: Use exact property names with dots, like linger.ms [OK]

Common Mistakes:

• Using underscores instead of dots
• Adding units like 'ms' in the value
• Using camelCase or colon syntax incorrectly

3. Given this Kafka producer config snippet:

props.put("batch.size", 16384);
props.put("linger.ms", 5);
props.put("acks", "all");

What is the expected effect on message sending?

medium

A. Messages batch up to 16KB or wait 5ms before sending, with full acknowledgment.

B. Messages are compressed automatically before sending.

C. Messages are sent immediately without batching.

D. Producer waits for only one replica acknowledgment.

Solution

1. Step 1: Analyze batch.size and linger.ms

   Batch size 16384 bytes means messages batch up to 16KB or linger 5ms before sending.

2. Step 2: Understand acks setting

   acks=all means producer waits for all replicas to confirm, ensuring durability.

3. Final Answer:

   Messages batch up to 16KB or wait 5ms before sending, with full acknowledgment. -> Option A

4. Quick Check:

   batch.size + linger.ms + acks=all = Messages batch up to 16KB or wait 5ms before sending, with full acknowledgment. [OK]

Hint: Batch size + linger.ms controls send timing, acks controls durability [OK]

Common Mistakes:

• Assuming messages send immediately ignoring linger.ms
• Confusing acks=all with acks=1
• Thinking compression happens automatically without config

4. You have this Kafka producer config:

props.put("batch.size", 32768);
props.put("linger.ms", 0);
props.put("acks", "0");

What is the main problem with this setup if you want high throughput and reliability?

medium

A. linger.ms=0 disables batching, reducing throughput.

B. acks=0 means no acknowledgment, risking message loss.

C. batch.size is too large and causes errors.

D. The config syntax is invalid and will cause exceptions.

Solution

1. Step 1: Check acks setting impact

   acks=0 means producer does not wait for any acknowledgment, risking message loss.

2. Step 2: Evaluate throughput vs reliability

   While batch.size is large and linger.ms=0 disables waiting, the main reliability issue is acks=0.

3. Final Answer:

   acks=0 means no acknowledgment, risking message loss. -> Option B

4. Quick Check:

   acks=0 risks loss despite throughput [OK]

Hint: acks=0 disables reliability, not good for safe throughput [OK]

Common Mistakes:

• Thinking linger.ms=0 disables batching completely
• Assuming batch.size too large causes errors
• Confusing config syntax as invalid

5. You want to optimize a Kafka producer for maximum throughput but still ensure messages are not lost. Which combination of settings is best?

hard

A. batch.size=512, linger.ms=50, acks=0, compression.type=lz4

B. batch.size=1024, linger.ms=0, acks=0, compression.type=none

C. batch.size=16384, linger.ms=0, acks=1, compression.type=gzip

D. batch.size=65536, linger.ms=20, acks=all, compression.type=snappy

Solution

1. Step 1: Maximize throughput with batching and linger

   Large batch.size (65536) and linger.ms (20ms) allow grouping many messages before sending.

2. Step 2: Ensure reliability and compression

   acks=all ensures all replicas confirm, preventing loss. Compression (snappy) reduces data size, improving throughput.

3. Final Answer:

   batch.size=65536, linger.ms=20, acks=all, compression.type=snappy -> Option D

4. Quick Check:

   Large batch + linger + acks=all + compression = batch.size=65536, linger.ms=20, acks=all, compression.type=snappy [OK]

Hint: Big batch + linger + acks=all + compression = best throughput + safety [OK]

Common Mistakes:

• Choosing acks=0 losing reliability
• Using too small batch sizes
• Ignoring compression benefits