Sending multiple commands in pipeline in Redis - Step-by-Step Execution

Concept Flow - Sending multiple commands in pipeline

Start Pipeline

↓

Queue Command 1

↓

Queue Command 2

↓

Queue Command N

↓

Send All Commands Together

↓

Receive All Responses

↓

Process Responses

↓

End Pipeline

Commands are queued first, then sent all at once to Redis, responses come back together, improving speed.

Execution Sample

Redis

MULTI
SET key1 value1
SET key2 value2
EXEC

Queues two SET commands in a transaction and executes them together.

Execution Table

Step	Action	Command Queued	Pipeline State	Response Received
1	Start pipeline	None	Empty queue	None
2	Queue command	SET key1 value1	Queue: [SET key1 value1]	None
3	Queue command	SET key2 value2	Queue: [SET key1 value1, SET key2 value2]	None
4	Send all commands	MULTI, SET key1 value1, SET key2 value2, EXEC	Queue sent	None
5	Receive responses	None	Queue cleared	Responses: [OK, QUEUED, QUEUED, [OK, OK]]
6	Process responses	None	Empty queue	Commands executed successfully
7	End pipeline	None	Empty queue	Pipeline finished

💡 All queued commands sent and responses received, pipeline ends.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
pipeline_queue	[]	[SET key1 value1]	[SET key1 value1, SET key2 value2]	Sent to Redis	[]	[]
responses	[]	[]	[]	[]	[OK, QUEUED, QUEUED, [OK, OK]]	[OK, QUEUED, QUEUED, [OK, OK]]

Key Moments - 2 Insights

Why don't we get responses immediately after queuing each command?

Responses come only after sending all commands together (see step 5 in execution_table), because pipeline queues commands first to send them in bulk.

What happens if we forget to send the queued commands?

Commands stay in the queue and no responses come back (see pipeline_queue state at step 4), so the pipeline never completes.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the pipeline state?

A Queue: [SET key1 value1]

B Queue sent

C Queue: [SET key1 value1, SET key2 value2]

D Empty queue

💡 Hint

Check the 'Pipeline State' column at step 3 in execution_table.

At which step do we receive the responses from Redis?

A Step 5

B Step 4

C Step 2

D Step 7

💡 Hint

Look at the 'Response Received' column in execution_table.

If we add another SET command before sending, how does the pipeline queue change at step 3?

A Queue sent

B Queue: [SET key1 value1, SET key2 value2, SET key3 value3]

C Queue: [SET key1 value1]

D Empty queue

💡 Hint

Refer to variable_tracker for pipeline_queue changes after queuing commands.

Concept Snapshot

Sending multiple commands in pipeline:
- Queue commands first without waiting for responses.
- Send all queued commands together to Redis.
- Receive all responses at once.
- Improves performance by reducing network delays.
- Use MULTI/EXEC or pipeline commands for batching.

Full Transcript

In Redis, sending multiple commands in a pipeline means you first queue commands without waiting for each response. Once all commands are queued, you send them together to Redis. Redis processes them and sends back all responses at once. This reduces the time spent waiting for each command individually, making operations faster. The example shows queuing two SET commands inside a MULTI/EXEC transaction. The execution table traces each step: starting the pipeline, queuing commands, sending them, receiving responses, and finishing. Variables like the pipeline queue and responses change state as commands are queued and sent. Key points include understanding that responses come only after sending all commands, and forgetting to send commands leaves the queue uncleared. The visual quiz tests understanding of pipeline state and response timing. The snapshot summarizes the main idea: queue commands, send together, get responses together, for better speed.

Practice

1. What is the main benefit of sending multiple commands in a Redis pipeline?

easy

A. It compresses the data before sending.

B. It reduces network round trips and speeds up command execution.

C. It automatically backs up the data.

D. It encrypts the commands for security.

Solution

1. Step 1: Understand what pipelining does

   Pipelining sends many commands at once without waiting for each reply, reducing network delays.

2. Step 2: Identify the main benefit

   This reduces the number of network round trips, making command execution faster.

3. Final Answer:

   It reduces network round trips and speeds up command execution. -> Option B

4. Quick Check:

   Pipelining = faster execution [OK]

Hint: Pipelining batches commands to save network time [OK]

Common Mistakes:

• Thinking pipelining encrypts commands
• Assuming pipelining compresses data
• Believing pipelining backs up data automatically

2. Which of the following is the correct way to start a Redis transaction pipeline?

easy

A. MULTI

B. PIPELINE

C. EXEC

D. BEGIN

Solution

1. Step 1: Recall Redis transaction commands

   Redis transactions start with the command MULTI to begin queuing commands.

2. Step 2: Confirm the correct command

   EXEC is used to execute queued commands, not to start the pipeline.

3. Final Answer:

   MULTI -> Option A

4. Quick Check:

   Start pipeline with MULTI [OK]

Hint: Start with MULTI, end with EXEC [OK]

Common Mistakes:

• Using EXEC to start instead of end
• Using PIPELINE which is not a Redis command
• Using BEGIN which is not valid in Redis

3. Consider the following Redis pipeline commands:

MULTI
SET key1 value1
SET key2 value2
EXEC

What will be the output of the EXEC command?

medium

A. [1, 1]

B. ["value1", "value2"]

C. Error: EXEC without MULTI

D. ["OK", "OK"]

Solution

1. Step 1: Understand MULTI/EXEC behavior

   Commands between MULTI and EXEC are queued and executed atomically when EXEC runs.

2. Step 2: Analyze the commands SET key1 value1 and SET key2 value2

   Each SET command returns "OK" on success.

3. Final Answer:

   ["OK", "OK"] -> Option D

4. Quick Check:

   SET commands return OK in EXEC output [OK]

Hint: SET returns OK, EXEC returns array of results [OK]

Common Mistakes:

• Expecting EXEC to return values set
• Confusing EXEC output with command errors
• Thinking EXEC returns numeric success codes

4. You wrote this Redis pipeline code:

MULTI
SET key1 value1
GET key1
EXEC

But the GET command returns nil instead of 'value1'. What is the likely cause?

medium

A. GET command is not supported inside MULTI/EXEC.

B. You forgot to call DISCARD after MULTI.

C. GET command runs before SET in the pipeline, so key1 is not set yet.

D. The key1 was deleted before EXEC.

Solution

1. Step 1: Understand command queuing in MULTI/EXEC

   Commands are queued and executed atomically, but GET inside MULTI returns nil because it reads before SET is applied.

2. Step 2: Explain why GET returns nil

   GET does not see the queued SET command's effect until after EXEC finishes.

3. Final Answer:

   GET command runs before SET in the pipeline, so key1 is not set yet. -> Option C

4. Quick Check:

   GET inside MULTI sees old data [OK]

Hint: GET inside MULTI reads old data, use EXEC results [OK]

Common Mistakes:

• Assuming GET works immediately inside MULTI
• Thinking DISCARD is needed here
• Believing GET is unsupported in transactions

5. You want to increment two counters atomically using Redis pipeline. Which sequence correctly uses MULTI/EXEC to do this?

hard

A. MULTI
INCR counter1
INCR counter2
EXEC

B. INCR counter1
INCR counter2

C. MULTI
INCR counter1
EXEC
INCR counter2
EXEC

D. PIPELINE
INCR counter1
INCR counter2
EXEC

Solution

1. Step 1: Identify atomic increment commands

   INCR commands increase counters by 1; to run atomically, they must be inside MULTI/EXEC.

2. Step 2: Check each option for correct pipeline usage

   MULTI
   INCR counter1
   INCR counter2
   EXEC

   queues both INCR commands inside MULTI and executes them together with EXEC.

3. Step 3: Explain why others are incorrect

   INCR counter1
   INCR counter2

   runs commands separately, not atomically.

   MULTI
   INCR counter1
   EXEC
   INCR counter2
   EXEC

   splits increments into two transactions.

   PIPELINE
   INCR counter1
   INCR counter2
   EXEC

   uses invalid PIPELINE command.

4. Final Answer:

   MULTI INCR counter1 INCR counter2 EXEC -> Option A

5. Quick Check:

   Atomic increments need MULTI/EXEC [OK]

Hint: Use MULTI before commands, EXEC after to run atomically [OK]

Common Mistakes:

• Running commands outside MULTI/EXEC for atomicity
• Using invalid PIPELINE command
• Splitting increments into separate transactions