Keepalive connections in Nginx - Time & Space Complexity

Time Complexity: Keepalive connections

O(n)

Understanding Time Complexity

We want to understand how the time cost changes when nginx handles multiple requests using keepalive connections.

How does keeping connections open affect the work nginx does as requests grow?

Scenario Under Consideration

Analyze the time complexity of the following nginx configuration snippet.

upstream backend {
    server backend1.example.com;
    server backend2.example.com;
    keepalive 16;
}

server {
    location / {
        proxy_pass http://backend;
        proxy_http_version 1.1;
        proxy_set_header Connection "";
    }
}
    

This config sets up a backend pool with 16 keepalive connections to reuse for multiple client requests.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Handling each incoming client request by reusing or opening backend connections.
• How many times: Once per client request, repeated for all requests.

How Execution Grows With Input

As the number of client requests increases, nginx maintains a pool of up to 16 idle backend connections, reusing them for multiple requests.

Input Size (n)	Approx. Operations
10	About 10 connection uses, mostly reused
100	Up to 16 new connections opened, 84 using reused connections
1000	Up to 16 new connections opened, 984 using reused connections

Pattern observation: Connection reuse helps reduce work per request but total work still grows roughly linearly with requests.

Final Time Complexity

Time Complexity: O(n)

This means the work nginx does grows directly with the number of requests, even with keepalive reuse.

Common Mistake

[X] Wrong: "Keepalive connections make nginx handle any number of requests instantly without extra work."

[OK] Correct: Even with reuse, each request still needs processing; keepalive just reduces connection setup time, not total work.

Interview Connect

Understanding how connection reuse affects request handling shows you can think about real server efficiency, a useful skill in many roles.

Self-Check

"What if we increased the keepalive value from 16 to 100? How would the time complexity change?"

Practice

1. What is the main benefit of using keepalive connections in nginx?

easy

A. They disable caching on the server.

B. They close connections immediately after each request.

C. They increase the number of open connections indefinitely.

D. They reuse the same connection for multiple requests, improving speed.

Solution

1. Step 1: Understand what keepalive connections do

   Keepalive connections allow the same connection to be reused for multiple requests instead of opening a new one each time.

2. Step 2: Identify the benefit of reusing connections

   Reusing connections reduces the time and resources needed to establish new connections, thus improving speed and reducing server load.

3. Final Answer:

   They reuse the same connection for multiple requests, improving speed. -> Option D

4. Quick Check:

   Keepalive = reuse connection for speed [OK]

Hint: Keepalive means reuse connection to speed up requests [OK]

Common Mistakes:

• Thinking keepalive closes connections immediately
• Believing keepalive increases open connections endlessly
• Confusing keepalive with caching

2. Which of the following is the correct syntax to set the keepalive timeout to 30 seconds in nginx?

easy

A. keepalive_timeout 30s

B. keepalive_timeout 30;

C. keepalive_timeout: 30s;

D. keepalive_timeout = 30;

Solution

1. Step 1: Recall nginx directive syntax

   Nginx directives use the format: directive_name value; without equal signs or colons.

2. Step 2: Check the correct value format for time

   Timeout values in nginx can be specified as numbers (seconds) without units or with units like 's'. Both are accepted, but the common practice is just a number for seconds.

3. Final Answer:

   keepalive_timeout 30; -> Option B

4. Quick Check:

   Directive syntax = name value; no '=' or ':' [OK]

Hint: Nginx directives use 'name value;' syntax without '=' [OK]

Common Mistakes:

• Using '=' sign in directive
• Adding colon ':' after directive name
• Adding units like 's' unnecessarily

3. Given this nginx configuration snippet:

keepalive_timeout 10;
keepalive_requests 100;

What happens after 100 requests on the same keepalive connection?

medium

A. The connection is closed and a new one is opened for the next request.

B. The connection stays open indefinitely.

C. The server resets the timeout to 10 seconds again.

D. The connection is closed immediately after the first request.

Solution

1. Step 1: Understand keepalive_requests directive

   This directive limits how many requests can be sent over one keepalive connection before it closes.

2. Step 2: Apply the limit of 100 requests

   After 100 requests, nginx closes the connection and opens a new one for the next request to avoid stale connections.

3. Final Answer:

   The connection is closed and a new one is opened for the next request. -> Option A

4. Quick Check:

   keepalive_requests = max requests per connection [OK]

Hint: keepalive_requests limits requests per connection [OK]

Common Mistakes:

• Thinking connection stays open forever
• Confusing timeout with request count
• Assuming connection closes after first request

4. You set keepalive_timeout 20; but clients report connections close too quickly. Which is the likely mistake?

medium

A. The keepalive_requests is set to 1, closing after one request.

B. The timeout value is too low for client needs.

C. You forgot to reload nginx after changing config.

D. The server is running an old nginx version without keepalive support.

Solution

1. Step 1: Check common reasons for config changes not applying

   If nginx is not reloaded or restarted after config changes, old settings remain active.

2. Step 2: Confirm reload necessity

   After changing keepalive_timeout, nginx must be reloaded with nginx -s reload or restarted to apply changes.

3. Final Answer:

   You forgot to reload nginx after changing config. -> Option C

4. Quick Check:

   Config changes need reload to apply [OK]

Hint: Reload nginx after config changes to apply them [OK]

Common Mistakes:

• Assuming timeout value alone fixes issue
• Ignoring need to reload nginx
• Blaming nginx version without checking

5. You want to optimize nginx for many short requests by keeping connections alive but closing them after 15 seconds or 50 requests, whichever comes first. Which configuration is correct?

hard

A. keepalive_timeout 15;\nkeepalive_requests 50;

B. keepalive_timeout 50;\nkeepalive_requests 15;

C. keepalive_timeout 15s;\nkeepalive_requests 50s;

D. keepalive_timeout 15s;\nkeepalive_requests 50; keepalive_disable none;

Solution

1. Step 1: Set keepalive_timeout to 15 seconds

   This controls how long a connection stays open waiting for new requests.

2. Step 2: Set keepalive_requests to 50

   This limits the number of requests per connection before closing it.

3. Step 3: Verify correct syntax and values

   keepalive_timeout 15;\nkeepalive_requests 50; uses correct syntax and values matching the requirement: 15 seconds timeout and 50 requests limit.

4. Final Answer:

   keepalive_timeout 15;\nkeepalive_requests 50; -> Option A

5. Quick Check:

   Timeout 15 + Requests 50 = correct config [OK]

Hint: Timeout sets seconds, requests sets max requests per connection [OK]

Common Mistakes:

• Swapping timeout and requests values
• Adding units to keepalive_requests
• Using invalid directives like keepalive_disable