Consumer prefetch optimization in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is consumer prefetch in RabbitMQ?

Consumer prefetch is the number of messages a consumer can receive and hold before acknowledging any of them. It controls how many messages are sent to a consumer at once.

intermediate

Why is prefetch optimization important in RabbitMQ?

Optimizing prefetch helps balance message throughput and resource usage. It prevents consumers from being overwhelmed and avoids message processing delays or memory issues.

intermediate

How do you set the prefetch count for a consumer in RabbitMQ?

Prefetch count is set using client libraries, e.g., channel.basic_qos(prefetch_count=10) in Python pika or equivalent in other clients. There is no direct RabbitMQ CLI command like rabbitmqctl for this; it's configured on the consumer/channel side.

beginner

What happens if the prefetch count is set too high?

If prefetch is too high, a consumer may receive many messages it cannot process quickly, leading to high memory use and slower message handling overall.

intermediate

What is a good strategy to find the optimal prefetch value?

Start with a low prefetch value, monitor consumer performance and resource use, then gradually increase it until you find a balance between throughput and resource consumption.

What does the prefetch count control in RabbitMQ?

A The size of the message payload

B The number of queues a consumer listens to

C The number of messages sent to a consumer before acknowledgment

D The number of consumers per queue

Prefetch count limits how many messages a consumer can receive before sending acknowledgments.

What is a risk of setting the prefetch count too low?

A Queue size increases indefinitely

B Consumer memory overload

C Messages get lost

D Consumer may be idle waiting for messages

Too low prefetch means the consumer waits for new messages too often, reducing throughput.

Which RabbitMQ feature helps you control message flow to consumers?

A Queue durability

B Prefetch count

C Exchange type

D Message TTL

Prefetch count controls how many messages a consumer can receive before acknowledging.

How can you adjust prefetch count in a RabbitMQ client?

A Using client library methods like channel.basicQos()

B Changing queue name

C Restarting RabbitMQ server

D Modifying exchange bindings

Client libraries provide methods to set prefetch count, such as basicQos in many RabbitMQ clients.

What is the effect of setting prefetch count to 1?

A Consumer processes one message at a time

B Consumer receives all messages at once

C Consumer ignores acknowledgments

D Queue deletes messages immediately

Prefetch count 1 means the consumer gets one message at a time and must ack before receiving another.

Explain what consumer prefetch optimization is and why it matters in RabbitMQ.

Think about how many messages a consumer can handle at once and why controlling that number helps.

Describe a step-by-step approach to find the best prefetch count for a RabbitMQ consumer.

Consider trial and error with monitoring.

Practice

1.

What does setting the prefetch_count in RabbitMQ control?

easy

A. The number of producers connected

B. The total number of queues in RabbitMQ

C. The maximum size of a message

D. The number of messages a consumer can receive before acknowledging

Solution

1. Step 1: Understand prefetch_count meaning

   The prefetch_count limits how many messages a consumer can get without acknowledging previous ones.

2. Step 2: Relate to consumer message handling

   This setting helps control consumer load by limiting unacknowledged messages.

3. Final Answer:

   The number of messages a consumer can receive before acknowledging -> Option D

4. Quick Check:

   prefetch_count controls message flow to consumer = D [OK]

Hint: Prefetch limits unacknowledged messages per consumer [OK]

Common Mistakes:

• Confusing prefetch_count with queue count
• Thinking it limits message size
• Assuming it controls producers

2.

Which of the following is the correct way to set prefetch_count to 10 using RabbitMQ's basic.qos command?

easy

A. channel.set_qos(10)

B. channel.prefetch(10)

C. channel.basic_qos(prefetch_count=10)

D. channel.qos(prefetch=10)

Solution

1. Step 1: Recall RabbitMQ client method for QoS

   The correct method to set prefetch count is basic_qos with prefetch_count argument.

2. Step 2: Match syntax with options

   channel.basic_qos(prefetch_count=10) uses channel.basic_qos(prefetch_count=10), which is the correct syntax.

3. Final Answer:

   channel.basic_qos(prefetch_count=10) -> Option C

4. Quick Check:

   basic_qos with prefetch_count sets limit = B [OK]

Hint: Use basic_qos(prefetch_count=number) to set prefetch [OK]

Common Mistakes:

• Using incorrect method names like set_qos or prefetch
• Passing wrong parameter names
• Confusing method with queue settings

3.

Given the following Python code snippet using pika library, what will be the effect of setting prefetch_count=5?

channel.basic_qos(prefetch_count=5)
for method_frame, properties, body in channel.consume('task_queue'):
    process_message(body)
    channel.basic_ack(method_frame.delivery_tag)

medium

A. Consumer will receive up to 5 unacknowledged messages at a time

B. Consumer will receive only 1 message at a time

C. Consumer will receive all messages without limit

D. Consumer will reject messages after 5

Solution

1. Step 1: Understand prefetch_count effect in code

   Setting prefetch_count=5 limits unacknowledged messages to 5 per consumer.

2. Step 2: Analyze message flow in loop

   The consumer processes and acknowledges messages one by one but can hold up to 5 unacknowledged messages simultaneously.

3. Final Answer:

   Consumer will receive up to 5 unacknowledged messages at a time -> Option A

4. Quick Check:

   prefetch_count=5 means max 5 unacked messages = A [OK]

Hint: prefetch_count sets max unacked messages per consumer [OK]

Common Mistakes:

• Thinking it limits to 1 message only
• Assuming unlimited messages are received
• Confusing reject with prefetch behavior

4.

Identify the issue in this RabbitMQ consumer code snippet that sets prefetch_count=0 and explain why it might cause problems:

channel.basic_qos(prefetch_count=0)
for method_frame, properties, body in channel.consume('queue'):
    process(body)
    channel.basic_ack(method_frame.delivery_tag)

medium

A. prefetch_count=0 disables prefetch, causing unlimited unacknowledged messages

B. prefetch_count=0 means no messages will be delivered

C. prefetch_count=0 causes syntax error

D. prefetch_count=0 limits to 1 message only

Solution

1. Step 1: Understand prefetch_count=0 meaning

   Setting prefetch_count=0 disables the limit, allowing unlimited unacknowledged messages.

2. Step 2: Explain potential problem

   This can overload the consumer with too many messages, causing memory or processing issues.

3. Final Answer:

   prefetch_count=0 disables prefetch, causing unlimited unacknowledged messages -> Option A

4. Quick Check:

   prefetch_count=0 means no limit, risk overload = A [OK]

Hint: prefetch_count=0 means unlimited messages, risky for consumers [OK]

Common Mistakes:

• Thinking 0 means no messages delivered
• Assuming it causes syntax error
• Believing it limits to 1 message

5.

You have a slow consumer that processes messages in 10 seconds each. To optimize throughput without overloading it, which prefetch_count value is best if you want to keep the consumer busy but not overwhelmed?

hard

A. 1

B. 10

C. 100

D. 0

Solution

1. Step 1: Analyze consumer speed and prefetch impact

   A slow consumer taking 10 seconds per message should have a prefetch count that allows some parallelism but avoids overload.

2. Step 2: Choose prefetch_count to balance load

   Setting prefetch_count to 10 allows the consumer to receive up to 10 messages unacknowledged, keeping it busy without too many messages queued.

3. Final Answer:

   10 -> Option B

4. Quick Check:

   Prefetch matches consumer speed for balance = C [OK]

Hint: Match prefetch to consumer speed to avoid overload [OK]

Common Mistakes:

• Setting prefetch too low causing idle time
• Setting prefetch too high causing overload
• Using 0 which causes unlimited messages