High Celery Question 180 of 228

How does worker_prefetch_multiplier affect fairness?

Python & Django · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: STACK VS QUEUE

StackLIFOlast in, first out

QueueFIFOfirst in, first out

Simple meaning

Prefetch pulls multiple messages per worker process to hide network latency.

WHY — Celery instead of guessing?

Why interviewers care about Celery:

This is a process

question about Celery.

Panels listen for order,

trade-offs, and what you would actually do on a Python project - not buzzwords.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

1
Prefetch pulls multiple messages
per worker process to hide network latency.
2
A high multiplier with
long tasks starves other tasks because a worker hoards the queue.
3
Lower it for mixed
runtimes, and use separate queues for bulk versus interactive jobs.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“A high multiplier with long tasks starves other tasks because a worker hoards th”

Break into beats

Ahighmultiplierwithlongtasks

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

Prefetch pulls multiple messages per worker process to hide network latency. A high multiplier with long tasks starves other tasks because a worker hoards the queue.