Pipeline vs individual commands performance in Redis - Visual Side-by-Side Comparison

Concept Flow - Pipeline vs individual commands performance

Start: Client wants to send multiple commands

↓

Send commands one by one

↓

Wait for each reply

↓

Process each reply

↓

Repeat for all commands

↓

Send all commands in a pipeline

↓

Send all commands at once

↓

Receive all replies at once

↓

Process all replies

↓

End

This flow shows two ways to send commands to Redis: individually waiting for each reply, or sending all commands together in a pipeline and then receiving all replies at once.

Execution Sample

Redis

SET key1 val1
SET key2 val2

This example shows two SET commands sent individually (waiting for each reply) or in a pipeline (buffered until flushed).

Execution Table

Step	Action	Command Sent	Waiting for Reply	Reply Received	Notes
1	Send SET key1	SET key1 val1	Yes	OK	Sent first command and waited for reply
2	Send SET key2	SET key2 val2	Yes	OK	Sent second command and waited for reply
3	All commands sent	N/A	No	N/A	Finished sending commands individually
4	Start pipeline	N/A	No	N/A	Begin pipeline mode
5	Send SET key1	SET key1 val1	No	No	Command buffered, no waiting
6	Send SET key2	SET key2 val2	No	No	Command buffered, no waiting
7	Flush pipeline	N/A	Yes	OK, OK	All replies received together
8	End	N/A	No	N/A	Pipeline complete

💡 Execution stops after all commands are sent and replies received either individually or via pipeline.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 5	After Step 6	After Step 7	Final
Commands Sent	0	1	2	1 (buffered)	2 (buffered)	2 (sent)	2
Replies Received	0	1	2	0	0	2	2
Waiting State	No	Yes	Yes	No	No	Yes	No

Key Moments - 3 Insights

Why does the client wait after each command in individual mode?

Because each command is sent separately and the client waits for the server's reply before sending the next command, as shown in steps 1 and 2 of the execution_table.

How does pipeline mode improve performance?

Pipeline mode sends all commands at once without waiting for replies, then receives all replies together, reducing network round trips as seen in steps 5 to 7.

What happens to replies in pipeline mode before flushing?

Replies are not received immediately; commands are buffered and replies come only after flushing the pipeline, shown in steps 5 and 6 where waiting is 'No' and replies are 'No'.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the client first wait for a reply in individual command mode?

A Step 5

B Step 1

C Step 3

D Step 7

💡 Hint

Check the 'Waiting for Reply' column in steps 1-3 for individual commands.

According to variable_tracker, how many replies are received after step 7 in pipeline mode?

A 0

B 1

C 2

D 3

💡 Hint

Look at the 'Replies Received' row after step 7.

If the client did not flush the pipeline, what would be the state of replies received?

A No replies received yet

B All replies received immediately

C Replies received one by one

D Replies lost

💡 Hint

Refer to steps 5 and 6 where commands are buffered but replies are not received.

Concept Snapshot

Pipeline vs Individual Commands Performance in Redis:
- Individual commands: send one, wait for reply, repeat.
- Pipeline: send many commands without waiting, then receive all replies together.
- Pipeline reduces network delays by minimizing round trips.
- Use pipeline for batch operations to improve speed.
- Remember to flush pipeline to get replies.

Full Transcript

This visual execution compares sending Redis commands individually versus using pipeline mode. Individually, each command is sent and the client waits for the reply before sending the next. This causes multiple network round trips. In pipeline mode, commands are sent all at once without waiting, then replies are received together after flushing. This reduces waiting time and improves performance. Variables like commands sent and replies received track the state changes. Key moments highlight why waiting happens in individual mode and how pipeline buffers commands. The quiz tests understanding of waiting steps, replies received, and pipeline flushing. The snapshot summarizes the main points for quick recall.