Why sendfile and tcp_nopush in Nginx? - Purpose & Use Cases

The Big Idea

What if your server could send files faster by skipping extra steps?

The Scenario

Imagine you run a busy website and every time a user requests a file, your server reads the file piece by piece and sends it over the network manually.

This means your server is juggling many small tasks, reading and sending tiny chunks repeatedly.

The Problem

This manual way is slow because the server spends extra time switching between reading files and sending data.

It also causes more network traffic with many small packets, making the website slower and less efficient.

The Solution

Using sendfile lets the server send files directly from disk to the network without extra copying.

Adding tcp_nopush groups small packets into bigger ones before sending, reducing network chatter.

Together, they make file delivery faster and smoother.

Before vs After

✗ Before

read file chunk
send chunk
repeat

✓ After

sendfile on;
tcp_nopush on;

What It Enables

This lets your server deliver files quickly and efficiently, improving user experience and saving resources.

Real Life Example

A video streaming site uses sendfile and tcp_nopush to smoothly send large video files without delays or buffering.

Key Takeaways

Manual file sending is slow and chatty.

sendfile sends files directly from disk to network.

tcp_nopush bundles packets for efficient delivery.

Practice

1. What is the main purpose of the sendfile directive in nginx?

easy

A. To compress files before sending them

B. To speed up file sending by avoiding extra copying between kernel and user space

C. To encrypt files during transfer

D. To limit the number of simultaneous connections

Solution

1. Step 1: Understand what sendfile does

   The sendfile directive allows nginx to send files directly from disk to the network socket without copying data to user space, which speeds up file sending.

2. Step 2: Compare options with this behavior

   Options B, C, and D describe unrelated features like compression, encryption, or connection limits, which are not the purpose of sendfile.

3. Final Answer:

   To speed up file sending by avoiding extra copying between kernel and user space -> Option B

4. Quick Check:

   sendfile = avoid extra copying [OK]

Hint: Remember: sendfile skips copying to user space [OK]

Common Mistakes:

• Thinking sendfile compresses data
• Confusing sendfile with encryption
• Assuming sendfile limits connections

2. Which of the following is the correct syntax to enable tcp_nopush in nginx configuration?

easy

A. tcp_nopush enable;

B. tcp_nopush = on;

C. tcp_nopush true;

D. tcp_nopush on;

Solution

1. Step 1: Recall nginx directive syntax

   In nginx, directives are set with the format directive value;. The correct value for enabling tcp_nopush is on.

2. Step 2: Check each option's syntax

   tcp_nopush on; uses tcp_nopush on; which is correct. Options A, C, and D use invalid keywords or syntax not supported by nginx.

3. Final Answer:

   tcp_nopush on; -> Option D

4. Quick Check:

   Enable directives with on; in nginx [OK]

Hint: Use 'on;' to enable nginx directives like tcp_nopush [OK]

Common Mistakes:

• Using 'enable' instead of 'on'
• Adding '=' sign in directive
• Using 'true' instead of 'on'

3. Given this nginx snippet:

sendfile on;
tcp_nopush on;

What is the expected effect on static file delivery?

medium

A. Files are sent faster by sending larger TCP packets

B. Files are sent slower due to extra copying

C. Files are compressed before sending

D. Files are sent with encryption

Solution

1. Step 1: Understand combined effect of sendfile and tcp_nopush

   sendfile on; avoids extra copying, and tcp_nopush on; allows grouping data into bigger TCP packets, improving speed.

2. Step 2: Analyze options

   Files are sent faster by sending larger TCP packets correctly states files are sent faster by sending larger TCP packets. Options B, C, and D describe incorrect effects.

3. Final Answer:

   Files are sent faster by sending larger TCP packets -> Option A

4. Quick Check:

   sendfile + tcp_nopush = faster large packets [OK]

Hint: sendfile + tcp_nopush = faster static file delivery [OK]

Common Mistakes:

• Thinking tcp_nopush compresses data
• Assuming sendfile slows down transfer
• Confusing tcp_nopush with encryption

4. You enabled sendfile on; but forgot to enable tcp_nopush. What issue might you observe?

medium

A. nginx configuration syntax error

B. Files fail to send completely

C. Small TCP packets causing inefficient network usage

D. Files get corrupted during transfer

Solution

1. Step 1: Understand the role of tcp_nopush with sendfile

   tcp_nopush helps group data into larger TCP packets. Without it, sendfile sends smaller packets inefficiently.

2. Step 2: Analyze consequences of missing tcp_nopush

   Small TCP packets causing inefficient network usage correctly identifies small TCP packets causing inefficient network usage. Options A, B, and D describe errors or corruption which do not happen just by missing tcp_nopush.

3. Final Answer:

   Small TCP packets causing inefficient network usage -> Option C

4. Quick Check:

   Missing tcp_nopush = small packets [OK]

Hint: Without tcp_nopush, packets stay small and inefficient [OK]

Common Mistakes:

• Expecting syntax errors without tcp_nopush
• Thinking files get corrupted
• Assuming files fail to send

5. You want to optimize nginx for serving large static files efficiently. Which configuration snippet correctly uses sendfile and tcp_nopush together?

hard

A. sendfile on;
tcp_nopush on;

B. sendfile on;
tcp_nopush off;

C. sendfile off;
tcp_nopush off;

D. sendfile off;
tcp_nopush on;

Solution

1. Step 1: Identify best practice for static file optimization

   To optimize static file delivery, sendfile should be enabled to avoid extra copying, and tcp_nopush enabled to send larger TCP packets.

2. Step 2: Evaluate each configuration snippet

   sendfile on; tcp_nopush on; enables both sendfile and tcp_nopush, which is the correct combination. Options A, B, and C disable one or both, reducing efficiency.

3. Final Answer:

   sendfile on; tcp_nopush on; -> Option A

4. Quick Check:

   Enable both for best static file speed [OK]

Hint: Enable both sendfile and tcp_nopush for best speed [OK]

Common Mistakes:

• Disabling sendfile but enabling tcp_nopush
• Enabling sendfile but disabling tcp_nopush
• Disabling both directives