Batch size and compression tuning in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the batch size for the Kafka producer.

Kafka

props.put("batch.size", [1]);

Drag options to blanks, or click blank then click option'

A1024

B16384

C512

D65536

Attempts:

3 left

💡 Hint

Common Mistakes

Using too small batch size reduces throughput.

Using too large batch size increases latency.

The batch size is typically set to 16384 bytes (16 KB) for efficient batching.

2fill in blank

medium

Complete the code to set the compression type for the Kafka producer.

Kafka

props.put("compression.type", [1]);

Drag options to blanks, or click blank then click option'

A"gzip"

B"snappy"

C"none"

D"lz4"

Attempts:

3 left

💡 Hint

Common Mistakes

Using compression type without quotes causes errors.

Choosing unsupported compression types.

Setting compression.type to "gzip" enables gzip compression for messages.

3fill in blank

hard

Fix the error in setting linger.ms to control batching delay.

Kafka

props.put("linger.ms", [1]);

Drag options to blanks, or click blank then click option'

A"5"

B5000L

C"5000"

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using string instead of integer causes runtime errors.

Using long literals is unnecessary here.

linger.ms expects an integer value, so 5 without quotes is correct.

4fill in blank

hard

Fill both blanks to create a producer config with batch size and compression type.

Kafka

props.put("batch.size", [1]);
props.put("compression.type", [2]);

Drag options to blanks, or click blank then click option'

A32768

B"snappy"

C"gzip"

D16384

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up batch size and compression values.

Using strings for batch size.

Batch size is set to 16384 bytes and compression.type to "gzip" for good performance.

5fill in blank

hard

Fill all three blanks to configure batch size, linger.ms, and compression type.

Kafka

props.put("batch.size", [1]);
props.put("linger.ms", [2]);
props.put("compression.type", [3]);

Drag options to blanks, or click blank then click option'

A32768

B10

C"snappy"

D16384

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings for numeric values.

Choosing unsupported compression types.

Batch size is 16384 bytes, linger.ms is 10 ms, and compression.type is "snappy" for balanced performance.

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